In-Place
Compilation:
In-place precompilation allows a developer or a site administrator to
access each page in the application as if it were being used by end users. This
means each page is compiled as if for ordinary use.
In-place precompilation takes place after the site is deployed but
before it goes public. To precompile a site in-place, you use the following
command, where /core35 indicates
the virtual folder of the application:
aspnet_compiler –v /core35
Precompilation
for Deployment:
Precompilation
for deployment generates a .le representation of the site made of assemblies,
static .les, and con.guration .les—a sort of manifest. This representation is
generated on a target machine and can also be packaged as MSI and then copied
and installed to a production machine. This form of precompilation doesn’t
require source code to be left on the target machine.aspnet_compiler [-?]
[-m metabasePath | -v virtualPath [-p physicalPath]]
[[-u] [-f] [-d] [-fixednames] targetDir]
[-c]
[-errorstack]
[-nologo]
[[-keyfile file | -keycontainer container ] [-aptca] [-delaysign]]
aspnet_compiler
–v /Core35 c:\ServerPath
Static .les such as images, web.con.g, and HTML pages are not compiled—they are just copied to the target
destination.
Warning If you don’t want to deploy
HTML pages as clear text, rename them to .aspx and compile them. A similar approach can be used for image .les. Note,
however, that if you hide images and HTML pages behind ASP.NET extensions, you
lose in terms of performance because IIS is used to process static files more
effciently than ASP.NET.
Web Site
Administration Tool:
WSAT is a distinct application that the ASP.NET setup installs with full
source. You .nd it under the ASP.NETWebAdminFiles
directory, below the ASP.NET build installation
path. This path is
C:\WINDOWS\Microsoft.NET\Framework\[version]
http://localhost:XXXX/asp.netwebadminfiles/default.aspx?applicationUrl=/Core35
