StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>This may sound a bit obvious, but I think it's something that is misunderstood because Visual Studio 2005 only shipped with the web site originally. If your project deals with a website that is fairly limited and doesn't have a lot of logical or physical separation, the website is fine. However if it is truly a web application with different modules where many users add and update data, you are better off with the web application.</p> <p>The biggest pro of the website model is that anything in the <code>app_code</code> section is dynamically compiled. You can make C# file updates without a full redeploy. However this comes at a great sacrifice. A lot of things happen under the covers that are difficult to control. Namespaces are difficult to control and specific DLL usage goes out the window by default for anything under <code>app_code</code> since everything is dynamically compiled.</p> <p>The web application model does not have dynamic compilation, but you gain control over the things that I have mentioned.</p> <p>If you are doing n-tier development, I highly recommend the web application model. If you are doing a limited web site or a quick and dirty implementation, the web site model may have advantages.</p> <p>More detailed analysis can be found in: </p> <ul> <li><em><a href="http://west-wind.com/weblog/posts/5601.aspx" rel="noreferrer">Web Application Projects and Web Deployment Projects are here</a></em></li> <li><em><a href="http://blogs.vertigo.com/personal/swarren/Blog/Lists/Posts/Post.aspx?ID=10" rel="noreferrer">Web Site or Web Application?</a></em></li> </ul>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload