Issues around converting ASP Website to ASP Web Application
<p>We have a web site built as an 'ASP.NET Website' type project, rather than the 'ASP.NET Web Application' type. </p>

<p>Aside from the obvious debugging advantages that the app type offers and access to the designer files for each page: </p>

<ol>
<li><p>What, if anything, can be gained by switching from website project type to app? </p></li>
<li><p>Are there performance losses with one over the other? </p></li>
<li><p>How much work is involved in switching an existing (dev) site from website to app? Is it as simple as creating another site as app type and adding these existing aspx files and libraries to it? </p>

<p>This question (<a href="http://stackoverflow.com/questions/735054/how-to-convert-asp-net-website-to-asp-net-web-application">http://stackoverflow.com/questions/735054/how-to-convert-asp-net-website-to-asp-net-web-application</a>) seems to cover the steps. </p>

<ul>
<li><p>What are the risks (if any?)</p></li>
<li><p>How much work should we plan on?</p></li>
</ul></li>
<li><p>Are there differences in how HTTP Application deals with requests or how handlers work between the two types? </p></li>
</ol>

<p>Anything we forgot to think of?</p>
