asp.net has its own compiler. just like version 1, a dll is created per
page (actually batching may cause more than 1 page per dll). the
difference is how the code behind classes are done. in vs2003 or vs2005
application model, the code behind file are compiled into one dll. in
vs2005 web site mode, the code behind code is included in the page dll.
take a simple site with 2 web pages.
page1.aspx -page1.aspx.cs
page2.apsx -page2.apsx.cs
for example with a vs2003 and vs2005 application you end up with 2 page
dlls built by the asp.net compiler and one code behind dll
page1.aspx.dll (name will depend on compilation model)
page2.aspx.dll (ditto)
project.dll (named by vs project)
in a vs2005 web site, only the first 2 dll's are built.
in vs2003/asp.net 1.0 the page dll's are built in a temp dir when the
web site is first accessed.
vs2005/asp.net support precompiling the page dll's into a deploy folder.
there are a couple modes depending on how you want to deploy updates.
you can fix the names, so that pages can be changed and deployed
individually (difficult with application mode), or whether the site is
redeployed in whole.
-- bruce (sqlwork.com)
Spam Catcher wrote:
Hi all,
From what I read, VS.NET 2005 doesn't precompile web applications into a
DLL for deployment, rather you need to manually precompile before release.
However, I have a web application in my project and it is compiling like in
.NET 1.1 - it is generating a set of deployment DLLs.
Does anyone know why it is doing that? Does VS.NET 2005 still support both
deployment models?
