Web Application project versus Web Site Project in Visual Studio [closed]?

I'm sure you'll get a lot of answers here - but from past experience working with both, I prefer Web Site Projects for 2 reasons: NO designer files to mess with. I don't know how many times I've had those get out of sync, and once they do, its a real pain to put things back into working order. Better PUBLISH functionality.

I prefer to fully compile my apps, and the publish wizard makes this all much simpler than the web apps do. Those 2 reasons above are the main reason I stick with web sites over web apps. There are probably plenty of other reasons why one or the other could be better - but between the 2 of those, web site projects let me spend much less time on making things work and more time coding.

I concur, Web Site is less hassle, unless you really need to pre-compile or something – Dan Diplo Aug 7 '09 at 19:24.

As an example: web application projects v.s. Web site projects website or webapplication in.ASP.NET.

Yes I did - on Google, but not in the SO search box. I usually go straight to Ask, type my title, then look through the suggested duplicates that pop up. For some reason, the results are not the same as the search.Thanks.

– Jeff Meatball Yang Aug 7 '09 at 19:46.

This is because running an individual page does not require that the whole site compile successfully, only the page and any components it depends on, such as code in the App_Code folder or the Global. It is easy to update a Web site in production. You can update individual source code files on the production server without having to explicitly recompile the site.

You can update individual files that are ready for deployment even if other files are not ready due to compile errors. You can also open the Web site on the production IIS server directly in Visual Studio and update the Web site in real time. Precompiling to multiple assemblies can have a performance advantage in some scenarios.

A typical example is a site that has many pages with lots of code written for them. Most of the pages are rarely requested and only some are used frequently. If you compile a site like this into multiple assemblies, the production server can load only the assemblies that are required for the current requests.

If a page is not requested, its corresponding assembly is not loaded.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.

Related Questions

» About WebKnox
» Contact
» WebKnox Blog
» RSS
» Newsletter
» Twitter
» API
» API Showcase