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
Labels:

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...
Post a Comment
Continue Reading »

Concept of App Domain in .Net

Creating Application Domains: Application domain is just like process, provides separate memory space, and isolates from other code. But it’s quite light weight. It also provides the following advantages: 1-       Reliability : If a domain crashes, it can be unloaded. Hence doesn’t affect the other assemblies. 2-       Efficiency : Loading all assemblies in one domain can be cumbersome and can make the process heavy but Appdomains are efficient in this manner. Important properties of AppDomain: ApplicationIdentity , ApplicationTrust , BaseDirectory , CurrentDomain , DomainManager , DomainDirectory , Evidence , FriendlyName , ID , RelativeSearchPath , SetupInformation , ShadowCopyFiles . Important methods of AppDomain: ApplyPolicy , CreateCOMInstanceFrom , CreateDomain , CreateInstance (Assembly). To create an AppDomain: AppDomain adomain = AppDomain.CreateDomain(“D”); To execute an assembly:...
Post a Comment
Continue Reading »

ASP.NET Working With Data-Bound Web Server Controls

Suppose we have: List<Car> vCars = new List<Car>(); There are three types of databound controls: Simple databound controls(List, AdRotater), Composite data bound controls(GridView, DetailsView, FormView that inherit from CompositeDataBoundControl), and Hierarchal data bound controls (TreeView, Menu).   DataBoundControl has a DataBind method that can be used when data is ready. It calls DataBind for child controls as well. Page.DataBind() will call DataBind for all child controls. Using DataSource Objects:                                       BaseDataBound control exposes DataSource property that accepts objects that implement IEnumerable , IListSource , IDataSource , or IHierarchalDataSource . DataSourceID accepts ID of SqlDataSource . If both specified Data...
Post a Comment
Continue Reading »