Project Description
This little project was at first designed to publish Web Projects done with the Express version of Visual Studio.

Recently i wanted to create a library(dll) containing User Controls. Well, this seems to be incompatible with the way VS and the .Net Framework works.
The only way to create such a library is to create a Web Application and publish it. This seems not to be very hard.
Nonetheless, when you publish a web site with Visual Studio, you do not have the choice of the output file's names. The consequence is that the reference changes as often as you create a new instance of Visual Studio. But you have also to change the registry tag on each page you use a custom control form the library.

I decided to enchance a bit the original application and add the possibility to build a Web User Control Library with a fixed name (thanks to ILMerge). The tool generate also a batch file from which you can easily make a shortcut in Visuam Studio Tools menu.

The UI is very simple:


The Output type allows you to choose if you want the output to be a WebSite or a WebUserControl Library. In fact it does not make much difference. If you choose WebUserControl Library output type the options will be checked automatically. You can have the same result if you choose the Web Site output. The WebUserControl Library output type is just a predefined configuration.

Application to build allows you to choose the WebApp to compile. Either choose an IIS site or a folder containing a WebApp with the command buttons on the right.

The Output Path allows you to choose where the files will be build.

Allow aspx files to be modified after publication will compile only the code behind so that the "XHTML" code will be editable.

Generate an assembly for each page or control will output, as it says, one assembly for each aspx and ascx files.

Merge all assemblies into one allows you to choose the name of the output assembly. This option uses ILMerge to merge all generated assemblies. The name of the file should have dll extension mentioned.

Create a batch file allows you to have a ready to use batch file to run the process without using the application.

When you are ready click on generate. Reference the generated dll in a WebApp application and use your user controls at will.

Last edited Jan 17, 2008 at 9:29 PM by ld9474, version 4