<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Precompiling Your Website</title><link>http://asp.net</link><pubDate>Thu, 31 Mar 2011 15:30:50 GMT</pubDate><generator>umbraco</generator><description>Comments for Precompiling Your Website</description><language>en</language><atom:link href="http://asp.net/rss/comments/33409" rel="self" type="application/rss+xml" /><item><title>Comment Posted by trainsoft</title><link>http://asp.net/web-forms/tutorials/deployment/deploying-web-site-projects/precompiling-your-website-vb</link><pubDate>Thu, 31 Mar 2011 15:30:50 GMT</pubDate><guid isPermaLink="false">00000000-0000-0000-0000000012665</guid><description><![CDATA[ <p>You indicate that ASP .NET provides two models to work with, the Web Application Project and the Web Site Project.  Actually, Web Sites are not projects at all: they don&#39;t conform to the VS Project structure, contain no .vbproj or .csproj files, are not built with MSBuild, and are not found in the New Project dialog box.  They are NOT generally referred to as WSP&#39;s (as they are not projects) as you say.</p><p></p><p>It is vital to seperate Web Sites from Web Application Projects because of the enourmous differences in capabilities and compliation each brings.  Calling a Web Site, a project (when it is not) just adds to this confusion.</p>]]></description><enclosure length="0" type="image/png" url="http://i2.asp.net/avatar/trainsoft.jpg?forceidenticon=false&amp;dt=635050413600000000&amp;enableAvatar=False&amp;cdn_id=2013-05-10-001" /></item></channel></rss>