Last post Aug 03, 2009 11:38 AM by hiren_andharia
Jul 31, 2009 07:02 PM|Klytus|LINK
I have a fairly large website (ASP.Net 3.5, C#) which is currently deployed with the source files on the live server. As we get closer to finishing the project, we want to start creating dll's for separate parts of the project, i.e. some helper classes
and user controls, such as menus, which no longer need constant updating.
So, my question is: How do I pre-compile only certain files in the solution to make dll's that the remaining pages can then reference?
Thanks for any general information on this.
Jul 31, 2009 07:57 PM|rtpHarry|LINK
You can change the batch attribute in the compilation tag of your web.config.
By setting it to false you will cause the compiler to compile everything into separate assemblies.
This will have the side effect of slowing down your compilation.
A better solution would be to separate different sections of your code out into Data Libraries. You would have to convert your website to a web application project so that you can contain more than one project under the umbrella of a solution. This is possible
in the full versions of Visual Studio and also the SP1 release of Visual Web Developer 2008 (it was added so MVC apps could support test projects)
Aug 01, 2009 01:22 AM|Klytus|LINK
Thank you, rtpHarry
I think I will go with the web application approach.
Aug 01, 2009 02:36 AM|Danny117|LINK
Its really easy. Take the first step. Create a project for the menu and reference the project with your solution and vs auto matically copies the dll into the bin folder. Tip: Don't forget to upload the bin folder to your server.
You can the above with express edtions and up.
Aug 01, 2009 09:56 AM|HostingASPNet|LINK
I agree that the application approach will be much better solution.
Aug 03, 2009 01:41 AM|Klytus|LINK
It's all done and worked like a charm!
Aug 03, 2009 11:38 AM|hiren_andharia|LINK
While Publish web site select option "Use fixed naming and Single assemblies" that will create seprate dlls for all pages