Win 2000LowerASP. NETConfiguration
By default, Windows 2000 (including Professional, Server, and Advanced Server) does not support ASP. . NET. It must be configured in an environment.
Client SQL Server. NET data provider Microsoft Data Access Component (MDAC) version 2.6 or later
Access to system Management information Windows Management Instrumentation (WMI) (installed together with the Windows 2000 operating system)
COM + Service Windows 2000 Service Pack 2.0
The SQL Server. NET data provider is installed on the Microsoft Data Access Component (MDAC) 2.7 or later, and restarts after installation.
ASP. NET Microsoft Internet info service (IIS) 5.0
Then download.. net framework and. install the. net framework sdk first. net framework. the two versions of net framework sdk must be the same. Currently, the most commonly used version is version 1.1. After installation, there will be four more things in the management tools in the control panel.
In addition, IIS will change accordingly, as shown in:
Is related to ASP. NET application ing.
Here, we need special tuning. You must first install iisand then install another program. Otherwise, you must use aspnet_regiis.exe to update the script ing.
The specific configuration is as follows:
To make it easier to reconfigure script ing for ASP. NET applications, each. NET Framework installation provides an associated ASP. net iis registration tool (Aspnet_regiis.exe) version. The administrator can use this tool to remap ASP. NET applications to the ASP. net isapi version associated with this tool.
Note that because Aspnet_regiis.exe is linked to a specific version of. NET Framework, the Administrator must use the appropriate version of Aspnet_regiis.exe to reconfigure script ing for ASP. NET applications. Aspnet_regiis.exe only reconfigured the script ing of ASP. NET applications to the ASP. net isapi version associated with this tool.
This tool can also be used to display the status of all installed ASP. NET versions, register the associated ASP. NET versions, create client script directories, and perform other configuration operations.
Use Aspnet_regiis.exe to update the script ing of an ASP. NET application
1. Open the command window. (Click Start, click Run, type cmd, and click OK ".)
2. Locate the directory of the Aspnet_regiis.exe version to be used. Remember that each version of the. NET Framework has its own version. Files are usually located in the following directory:
System Root \ Microsoft. NET \ Framework \ version
3. Use the-s or-sn option of Aspnet_regiis.exe together with the Application Path to set script ing. The following shows a command line example that updates the script ing of an application named SampleApp1.
Aspnet_regiis.exe-s W3SVC/1/ROOT/SampleApp1
The following is an example of image operations.
Disable automatic update of script ing
To prevent all existing applications from automatically remapped to the. NET Framework version being installed, use the/noaspupgrade command line option when running the Dotnetfx.exe installation program. The entire command line is shown below.
Dotnetfx.exe/c: "install/noaspupgrade"
Uninstall a certain version of ASP. NET
If you have installed multiple versions of ASP. NET on a computer, you can uninstall a specific version. To uninstall ASP. NET, You can uninstall the. NET Framework by using the "add or delete programs" item in "Control Panel. During the uninstall process, the installer uses the-u option (uninstall flag) to call ASP. net iis registration tool (Aspnet_regiis.exe ).
Note that if you only want to uninstall a certain version of ASP. NET without detaching the associated. NET Framework, you can directly use Aspnet_regiis.exe .. . NET Framework. If you only uninstall ASP. NET, use the-u option of the tool Version associated with the ASP. NET version you want to uninstall. For more information, see ASP. net iis registration tool (Aspnet_regiis.exe ).
The-u option of Aspnet_regiis.exe performs the following operations:
All ASP. NET Applications mapped to the current ASP. NET version to be uninstalled will be remapped to the next latest compatible version on the computer. If no compatible version exists, the script ing of the application will be completely deleted.
Warning after deleting the script ing, IIS submits the ASP. NET page in text format. This may expose the source code to the client.
ASP. NET status services are shared by all compatible ASP. NET versions and are always mapped to the latest installed version of ASP. NET. If the ASP. NET version you want to uninstall is the latest version, the next compatible version on the computer will be registered to replace this version. If no compatible version exists, ASP. NET status service will be uninstalled.
Performance objects and associated performance counters specific to the version to be detached will be deleted. General performance objects and counters for all ASP. NET, ASP. NET, and ASP. NET application versions installed will be directed to the latest installed version on the computer.
The ASPNET user account is shared by all compatible ASP. NET versions. If no other ASP. NET installation exists on the computer, the ASPNET User Account and the associated access control list will be deleted.
Script ing of ASP. NET Applications
If multiple versions of the. NET Framework are installed on the same computer, these installations each contain an associated ASP. net isapi version. ASP. NET applications use ASP. net isapi to determine which version of. NET Framework the application uses. NET Framework. ASP. NET applications can be configured to use any version of the installed ASP. net isapi. To specify the ASP. net isapi version used by an ASP. NET application, you should register script ing for the application in Internet Information Service (IIS.
Script ing Associates file extensions and HTTP predicates with appropriate isapis for script processing. For example, if IIS receives. aspx file request, the script ing of the application instructs IIS to send the requested file to the appropriate version of ASP.. net isapi. Script ing of each ASP. NET application is usually set in the Internet information service console. It can be applied directly to an application or inherited from the parent application. Installed by default. NET Framework, all existing ASP.. NET application script ing to use ASP.. net isapi version, unless the application uses a later or Incompatible version.
To make it easier to reconfigure script ing for ASP. NET applications, each. NET Framework installation provides an associated ASP. net iis registration tool (Aspnet_regiis.exe) version. By default, the tool is installed in the following directory:
<System root> \ Microsoft. NET \ Framework \ <version number> 〉
The administrator can use this tool to remap ASP. NET applications to the ASP. net isapi version associated with this tool.
Note that because Aspnet_regiis.exe is associated with a specific version of. NET Framework, the Administrator must use the appropriate version of Aspnet_regiis.exe to reconfigure script ing for ASP. NET applications. Aspnet_regiis.exe only reconfigured the script ing of ASP. NET applications to the ASP. net isapi version associated with this tool.
This tool can also be used to display the status of all installed ASP. NET versions, register the associated ASP. NET versions, create client script directories, and perform other configuration operations.
The following is a demonstration of a small ASP. NET operation process.
Create an EXAMPLE1.ASPX file and use NotePad to open the file and enter
Or
Here I want to explain two points: 1. My example files are always written in C # and VB for A and B respectively, and the demo images are written in C, they are all the same. The code in the tutorial is also written in two separate methods. You can compare them. 2. When I write the tutorial, I use NotePad to write APS. NET, you can also install. NET, but it is better to use Notepad, because it can be viewed more thoroughly.
The following uses an image to describe the operation process:
I believe that at this time you have a comprehensive understanding of ASP. NET under win2000. You can also debug some ASP. NET code and start to have close contact with ASP. NET. We also hope that you will increase your interest in ASP. NET and join us in learning ASP. NET to enjoy the fun of ASP. NET.