ASP.Net Web Site Project vs. Web Application Project [duplicate]

Question

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 separate dll in the web application project?
• Are there some prohibitive (performance,memory?) costs to compiling each page's code behind into separate 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?

Answer 1

I'd say if everyone there needs the flexibility to deploy bug fixes post release without re-releasing the whole site then they are right: you need to have a web project for that sort of dynamic compilation. That or a better testing process ;)

Personally I prefer a web application though since there is only one dll created, which means less mess and less scope for "weird bugs" with dll's having different names etc. If you have a large site you should really be using a web application. I remember making this decision a year ago and I never looked back (I chose web application) :)