conversion of website project to webapp projecthttp://forums.asp.net/t/1799675.aspx/1?conversion+of+website+project+to+webapp+projectFri, 04 May 2012 23:25:25 -040017996754963749http://forums.asp.net/p/1799675/4963749.aspx/1?conversion+of+website+project+to+webapp+projectconversion of website project to webapp project <p>&nbsp;</p> <p>Hi,</p> <p>I am using VS2010.My clients applications are in .Net 1.1 frame work .,I need to move them to 4.0.</p> <p>While the conversion my manager told to right click on the project and do convert to web app</p> <p>Why am supposed to do that?It generated some designer and code(auto-gen)</p> <p>What if we dont do conversion to web app</p> <p>&nbsp;</p> 2012-05-03T12:22:45-04:004965923http://forums.asp.net/p/1799675/4965923.aspx/1?Re+conversion+of+website+project+to+webapp+projectRe: conversion of website project to webapp project <p>this link (uploaded by my cooleague) explains clearly the difference between them. well i mostly use websites because they are easier to deploy :-)</p> <p>http://www.codersbarn.com/post/2008/06/01/ASPNET-Web-Site-versus-Web-Application-Project.aspx</p> 2012-05-04T15:28:45-04:004966388http://forums.asp.net/p/1799675/4966388.aspx/1?Re+conversion+of+website+project+to+webapp+projectRe: conversion of website project to webapp project <p><a href="http://vishaljoshi.blogspot.com/2009/08/web-application-project-vs-web-site.html">http://vishaljoshi.blogspot.com/2009/08/web-application-project-vs-web-site.html</a>&nbsp;is one of the more thorough comparisons of Web Application Projects (WAP) and Web Site Projects (WSP).&nbsp; It's a pretty good read.</p> <p>From your post, I'm assuming that you'ce converted to a WAP.&nbsp; The main difference between WAP and WSP is that a WAP builds all of the source files (pure code files that is, so not including the .aspx/ascx itself) into a DLL in the bin directory; in this model, you compile first, then deploy.&nbsp; In a WSP, the source files are all deployed and compiled on the fly (including class files in App_Code); there isn't a compliation phase per say until you've deployed the site.&nbsp; (There are ways to pre-compile a WSP, but I won't go into those here.)</p> <p>When dealing with a WSP, Visual Studio gets type information from that on-the-fly compilation, by leveraging the runtime's compiler and then getting data from that output.&nbsp;</p> <p>However, for WAP, we do it by building the project and using the same support as all other compiled project types.&nbsp; The designer files that we generate in a WAP are to keep the compiled binary in sync with the markup file contents.&nbsp; For example, if you have &lt;asp:Button ID=&quot;fooButton&quot; runat=&quot;server&quot;/&gt; in the markup file, the designe file will have a member that corresponds to this.&nbsp; Then when you're in code-behind, you can reference fooButton through the regular language services in Visual Studio.</p> <p>I hope this clarifies why the designer files are needed. :)</p> 2012-05-04T23:25:25-04:00