Skip to main content

In-Place Compilation in ASP.NET



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]

Running WSAT Manually:

http://localhost:XXXX/asp.netwebadminfiles/default.aspx?applicationUrl=/Core35

Popular posts from this blog

Culture Information and Localization in .NET

Namespace: System.Globalization CultureInfo Class:                 It provides information like the Format of numbers and dates, Culture’s Calendar, Culture’s language and sublanguage (if applicable), Country and region of the culture. The Basic use of CultureInfo class is shown here: • How string Comparisons are performed • How Number Comparison & Formats are performed • Date Comparison and Formats. • How resources are retrieved and used. Cultures are grouped into three categories: Invariant Culture : It’s Culture Insensitive. It can be used to build some trial application. It can be also used to build an application with hard-coded expiry date that ignores cultures. But using it for every comparison will be incorrect and inappropriate. Neutral Culture : English(en), Frensh(fr), and Spanish(sp). A neutral culture is related to language but it’s not related to specific regi...

Exposing .NET Components to COM

Namespace: System.Runtime.CompilerServices Building .NET Components for use by COM .Net framework generates COM Proxies known as COM Callable Wrapper (CCW) to be used by COM. No matter how many COM clients consume a given managed object, .Net runtime will create a single CCW. Write down you class and before building it, Select the configuration form the project properties named “ Register for COM interop ”. Hiding public .NET Classes from COM To hide a class or member just use the following attribute: [ComVisible(true/false)] . Deploying COM-Enabled Assemblies :       Check the following necessaries before creating CCW: 1.        All class have default constructor (no parameter). 2.        Exposed Types should be public . 3.        Any member exposed should be public . 4.        Abstract classes will not b...

ASP.NET Working with Web Configuration Files

Our sites are configured based on hierarchy of XML configuration files. Machine.config is top level configuration file located in Config: %WINDIR%\Microsoft.NET\Framework\ <version> \Config\machine.config These settings are framework level and common to all Windows, Console, Class Library, and Web application. Some of them could be overridden in Web.config while others are protected. Next in hierarchy is Root.config. It’s located in Config: %WINDIR%\Microsoft.NET\Framework\ <version> \Config\web.config It contains default web server settings. Optionally one can add at root of all websites a web.config to provide general settings related to all sites. Optionally to provide more control on settings one can add web.config in each web site and for each folder in that web site. Processing the Configuration files:                       ...