ASP. NET 2.0 release issues)

Yesterday, a friend in a QQ Group asked me how to publish (compile) Asp. net2.0)ProgramTo generate the DLL.
However, the vwd2005 express we obtained from Ms does not support the release of DLL.
You can use aspnet_compiler.exe to publish our project.

Yesterday, I got a. NET Framework 2.0 software development kit (SDK) Beta 2x86 from Ms.
Http://www.microsoft.com/downloads/details.aspx? Familyid = 10970791-8912-4f94-ac46-7ce0e1_d5c9 & displaylang = en
After installation, select this project through the Start Menu/Program/mrcrosoft. Net framwoks SDK 2.0/SDK Command Prompt
The dos interface path is c: \ Program Files \ microsoft_visual_studio_8 \ SDK \ V2.0>

We can use aspnet_compiler.exe.
If you use this command, enter aspnet_compiler -? Enter
The parameters are all used and are still in Chinese, which is much more convenient.

C: \ Program Files \ microsoft_visual_studio_8 \ SDK \ V2.0> aspnet_compiler -?
Utility used to pre-compile ASP. NET Applications
Copyright (c) Microsoft Corporation. All rights reserved.

Usage:
Aspnet_compiler [-?] [-M metabasepath |-V virtualpath [-P physicaldir]
[[-U] [-F] [-D] targetdir] [-C] [-fixednames]
[-Keyfile file |-keycontainer container [-apchloroform] [-delaysign]

-? Print the help text.
-Complete IIS metabase path of the M application. This switch cannot be combined with the-V or-P switch.
-V indicates the virtual path of the application to be compiled (for example, "/MyApp "). If-P is specified, use
Locate the application in the physical path. Otherwise, use IIS
Metadatabase, and assume that the application is located at the default site (under "/lm/w3svc/1/root ). This
The switch cannot be combined with the-M switch.
-P: physical path of the application to be compiled. If-P is missing, use the IIS metadatabase to locate this
Application. This switch must be combined with-v.
-U if specified, the pre-compiled application is updatable.
-F if the target directory already exists, rewrite it. The existing content will be lost.
-D if this option is specified, debugging information will be sent during compilation.
The physical path to which the targetdir application will compile. If this parameter is not specified, the application is precompiled locally.
-C if specified, the entire pre-compiled application is regenerated. Any previously compiled component will
Re-compiled. In the specified targetdir
Always enable this option.
-The physical path of the Keyfile with a strong name.
-Keycontainer: specify a strong-name key container.
-If apchloroform is specified, a strongly-named assembly allows some trusted callers.
-If delaysign is specified, the Assembly is not fully signed after creation.
-If fixednames is specified, the compiled assembly will have a fixed name.
-Nologo: cancels the copyright message of the compiler.

Example:

The following two commands are equivalent and depend on the IIS metadatabase. The compiled application is deployed to c: \ mytarget:
Aspnet_compiler-M/lm/w3svc/1/root/MyApp c: \ mytarget
Aspnet_compiler-V/MyApp c: \ mytarget

Run the following command to compile the application/MyApp locally. In this way, no compilation is required when an HTTP request is sent to it:
Aspnet_compiler-V/MyApp

The following command does not depend on the IIS metadatabase because it explicitly specifies the physical source directory of the application:
Aspnet_compiler-V/MyApp-p c: \ MyApp c: \ mytarget

C: \ Program Files \ microsoft_visual_studio_8 \ SDK \ V2.0>