Shulou(Shulou.com)06/02 Report--

This article mainly describes how to deploy ASP.NET applications, the article is very detailed, has a certain reference value, interested in small partners must read!

1. Use the "Copy Project" function of VS. NET to deploy--source code mode. In VS. NET, you can directly copy the source code to the target server. In the Solution Explorer, you can see a "Copy Web Site" tool button. Refer to the following figure:

Click the Change button to open the Copy Web Site window in VS. NET, as shown below.

The entire inner form is roughly divided into two sections: Source Web site: now the local Web application resource, Remote Web site shows the remote Web application resource (that is, the location of the target file you want to upload)

But as you may have seen, the Remote Web site is grayed out and unavailable, so you need to connect to the remote server as well.

On the Copy Web Site toolbar, there is a Connect button. Click it and the Connect option appears. As shown in the figure, this is exactly the way to open the Web described earlier. The slight difference is that here you are deploying ASP.NET applications. You can now log in remotely using the account given to you by your internet service provider. The login shown here is a web server within the local area network, and the location to upload is under the www folder.

Once you log in successfully, you can deploy ASP.NET applications, as shown in the figure, when you select files, you can synchronize local and remote server files, it should be noted that here is "synchronization" rather than simple copy. The advantage is that when you are local or remote higher, you can synchronize later, and the files on both sides can be updated synchronously.

2. Use Public Web Site to deploy ASP.NET applications-source code + binary

You can deploy precompiled applications using the Public Web Site provided by VS.NET. This is similar to ASP.NET 1.1. To launch a public web site, select "Public Web Site" from the Build menu of VS. NET as shown in the figure below. This will bring up the Public Web Site dialog box as shown in the figure below.

In this diagram, you need to enter the address of the remote server, which can be HTTP, FTP, etc. Here we use the local machine as a test, enter http://localhost, which will create the MyFirstPage project in the current IIS home directory. In the check box below, the instructions are as follows:

◆Allow this precompiled site to be updatable: This option allows *.aspx not to be compiled into the report set, which means that you can change the markup of the page after checking this option.

Use fixed naming and single page assemblies: This option runs code that you precompiled for specific file names.

Enable strong naming on precompiled assemblies: This option requires that renamed assemblies be generated. Default values are used here. Then click "OK," and after compilation, you will find these precompiled files in the IIS home directory.

If you open MyPage.aspx, the code is as follows:

UntitledPage

Enteryourname:

As mentioned earlier, since the Page directive is

CodeFile is not included, so this compilation is compatible with ASP.NET 1.1.

The inherits of the Page directive indicates that the class set of MyPage.aspx is MyPage and the assembly set App_Web_jmvb-kmt. In other words, when the system loads Page, it will load MyPage class into App_Web_jmvb-kmt.dll under bin folder as page class of MyPage.aspx background file.

3. Deploy applications using Aspnet_compiler.exe

Aspnet_compiler.exe is a new command added to ASP.NET 2.0, so it is not available for previous versions of the. NET Framework. You can find it in the installation directory, for example, c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727 directory.

Aspnet_compiler.exe provides many parameters, you can type Aspnet_compiler. exe/? on the command line. See what these parameters mean. Here are a few parameters we use for this introduction:

The- m m parameter tells the system to configure the application using IIS metadata, such as the following command

aspnet_compiler -m /LM/W3SVC/1/Root/MyApp c:\MyTarget

/LM /W3SVC/1/Root represents the configuration information of the HTTP service we want to use, and there is a "Server Extensions Manager" in the "Control Panel". You can open your own configuration. In this command, it indicates that the current application is MyApp, and the physical path of the file used by the application is c:\MyTarget

2 -vv represents the virtual path of the application. If both are used in conjunction with the-p parameter, the-p parameter indicates the physical path, otherwise IIS's elemental data configuration is used, which defaults to the current site of the application.

Order below and register above.

aspnet_compiler -v /MyApp

The following does not rely on IIS configuration because it shows the physical path of the declared application

aspnet_compiler -v /MyApp -p c:\myapp c:\MyTarget

-u

v virtualPath -The virtual path of the application

-p physicalPath -Event location of the application

targetDirectory -target location

There is also a parameter: u, which tells the compiler to keep the *.aspx page for future updates, in this case in the form of the "assembly + binary" code described above

We'll show you how to use this command below, and further explain the changes deployed from ASP.NET 1.1 to ASP.NET 2.0.

The following code illustrates how to deploy an ASP.NET application using aspnet_compiler for one of the following situations:

I used the built-in server of VS. NET 2005 and created MyFirstPage project in my document C:\Documents and Settings\liwanbao\My Documents\Visual Studio 2005\WebSites using File System mode.

Now I want to deploy this program to the local IIS server vendor. In IIS server, my application name is DeplayApp, and the actual path that the application points to is D:\DeplayMyFirstPage, so if you open IIS, you should see something like this

In fact, here are the three parameters commonly used in aspnet_compiler.exe described above

DeplayApp is the virtual path of the application, that is, the path specified by the-v parameter above.

D:\DeplayMyFirstPage is the actual physical path corresponding to the virtual path, that is, the target path to which I want to deploy

C:\Documents and Settings\liwanbao\My Documents\Visual Studio 2005\WebSites path is where I developed the project source code.

In the command above, first set the Path path to aspnet_compiler.exe to prevent the system from finding the command. The specific command is

aspnet_compiler -v /DeplyApp-p MyFirstPage d:\DeplayMyFirstPage

This will create the required file (*.aspx) in the D:\DeplayMyFirstPage directory, and the database file for the application can be found in the App_Data directory. Note that when referring to the database, the current location of the App_Data file is applied, for example, the database connection is

Because the absolute location of DotNetEntry_Data.MDF is specified, the destination file does not protect the App_Data file bin folder. It stores the compiled DLL file and also contains references to the assembly. For example, use Notepad to open default.aspx.cdcab7d2.compiled. Similar code is as follows:

This is a marker file generated by the precompilation tool, and should not be deleted!

You may ask why *.aspx files are needed if they are all DLL files. These documents also have no specific content. Could they be redundant? To understand this problem, you need to go to IIS, which means that this is no longer the work of ASP.NET2.0. For client requests, IIS will first check whether the file you requested exists according to the mapping, and if it does not exist, it will directly prompt you that the requested file has not been found.

That's all for "How to deploy ASP.NET applications." Thanks for reading! Hope to share the content to help everyone, more relevant knowledge, welcome to pay attention to the industry information channel!

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.