Web Projects

Web projects

	How To Get Design-Time Support for DNN Controls As everyone that is a regular reader of this blog is already aware of I am a big fan of the WAP development model for all DotNetNuke development projects. Now, one of the most common issues that individuals have reported to me is that "design-time" support is not there for common DotNetNuke user controls that are common to integrate with custom modules. The controls I'm discussing are the DNN Label, Text Editor, and Url Controls. Luckly though it is VERY simple to get full design time support for the controls and this article will show you how to accomplish this!
	DotNetNuke CSharp Web Application Project Past versions of DotNetNuke typically came with a source code release and an installation release. Many developers (myself included) look at DNN as a platform and prefer not to touch the DNN source code. Once you start tweaking the source code, you open up a world of headaches if you plan on upgrading to the next version of DNN since you add the pain of making sure to migrate your own changes. DNN provides plenty of integration and extensibility points that for the most part, touching the source code is unnecessary.
	Using Web Application Project(WAP) for development of DotNetNuke modules with Edit and Continue Supp My VS solution consists of main WAP Project and one or more User Control Libraries similar to described in Tutorial 6: Creating and Using User Control Libraries. The main WAP Project basically includes one DNNDebug.aspx file (as well as web.config and global.asax), that allows me to load and test my user controls. The User Control Libraries(DNN modules) are physically located in DesktopModules subfolder of the main project, so I don’t need to copy ascx files from control library to main project subfolders as it is recommended in the Tutorial

PA 's

	DotNetNuke Module Packaging for the Terminally Broke So, you've been dabbling with DNN modules for a while, and now you've written something you'd like to sell. But you don't fancy giving away your source code - what to do, what to do? If you've been looking around a bit, you've probably come across Michael Washington's article on how to package your DNN module as a compiled assembly. Great article, one drawback: this won't work if you are one broke developer, using Visual Web Developer Express (because it's free, hooray!).
	Packaging your DotNetNuke® Module You want to create a DotNetNuke module and you want to distribute it but you don't want to give away your source code?
	Automating aspnet_compiler in Visual Web Developer Visual Studio has a cool user interface for publishing a website using the Publish Web Site dialog, accessible by selecting Build, Publish Web Site. You can use this dialog to pre-compile your website and avoid having to deploy source code.
	How to publish a web project with MSBuild? How to publish a web project with MSBuild?