You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

The ASP.NET 2.0 compiler action allows you to precompile ASP.NET 2.0 applications before deployment.

Precompiling has two main advantages:

Application Path

There are three ways to specify the path to your ASP.NET Application:

IIS Virtual Path Andamp; Physical Directory Determined by IIS

The application will be located by using the IIS metabase and the default website. The physical (local) folder will be determined via the IIS metabase.

IIS Virtual Path Andamp; 'Use Physical Directory'

The application will be compiled from the specified physical (local) directory, but as if it was installed at the IIS virtual directory given by the path. This is useful if you want to compile your ASP.NET application from one (offline) directory, but deploy the assemblies in another directory.

Full IIS Metabase Path

The application will be located by using a full IIS metabase path. The physical (local) folder will be determined via the IIS metabase.

Framework Version

Specify the .NET framework version that you want to compile with. The ASP.NET 2.0 Compiler action requires .NET 2.0.

Target Output Directory

Compile the application in-place

The application will compile to the same directory as the source.

Fully rebuild target application : All sources will be rebuilt, not just those which have changed.

Compile the application to target directory

The application will compile to the specified target directory. Compiling to a target directory automatically implies "fully rebuild target application."

Create updatable application : The compiled application will be updatable.

Overwrite the target directory : If the target directory already exists, its contents will be overwritten.

Emit debug information : The compiler will emit debug information to the log during the compile process.

Use fixed names for compiled assemblies : The compiled assemblies will be given fixed names.

(If this option is not set, the names will be autogenerated.)

The compiled application assembly can be signed with a strong name from a key file or key container. If using a key container, the application can be set to allow partially trusted callers or to not fully sign the compiled assembly.

  • No labels