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 »

Using ADO.NET Transaction Object, Saving CLR Objects and SqlNotificationRequest

Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : A transaction can’t span multiple connections.   Local and distributed transaction ares supported in 1.x you have to Enterpeise seveices library to regiser multiple connections and then call EnlistDistributedTransaction. Distributed Transaction Coordinator is required for Distributed transaction that’s available on windows 2000 & +. In 2.X and later use TransactionScope object. Serializable allows one transaction to complete before the other start. SqlConnectoin support named savpoint to roll back to; that’s an equaliant to save transaction command in MS SQL Server. Using TransactionScope Object : Dispoase of the transaction must be called to complete the transaction. Distributed Transaction : ...
Continue Reading »

Code Access Security in .Net

Namespace: System.Security What is Code Access Security? Code Access Security is a mechanism through which Developers and administrators can restrict code from accessing different resources , without caring about the users’ access level. You can also control resource that can’t be controlled through traditional RBS (Role Based Security), e.g. Web Requests and DNS requests etc. It can be only applied to Managed Applications. These restriction are applied not to the user instead to the Application, thus it does not require username or password. Evidence: It is the information that runtime gather about the assembly to determine which Code Groups the assembly belongs to. The following table shows the common types of evidence that a host can present to the runtime. Evidence Description Application directory The application's installation directory. Hash Cryptographic hash such as SHA1. Publisher Soft...
Post a Comment
Continue Reading »