ASP.Net Web Site Project vs. Web Application Project
- by user144612
I'm trying to convince my co-workers to switch from a web site project to a web application project, because I want the use of the project file. However I can't diffuse this argument against:
The web site project allows each page to be compiled into a single dll. Their argument is this enables easy fixing of errors found after publishing. This is contrast to how the web application project compiles all code behind into a single dll.
Is updating a single page's dll essentially different to updating the entire site's dll?
Is there some way to compile each page's code behind into a seperate dll in the web application project?
Are there some prohibitive (performance,memory?) costs to compiling each page's code behind into seperate dll's that we are unaware of?
Why is the feature(?) to compile each page to separate dlls in web site projects and not web app projects?