In parallel with the .NET Frame 1.0 and 1.1.
In ASP.NET, the application installed on the same computer can perform parallelism using different versions .NET framework. The following topics describe how to configure the ASP.NET application executed in parallel, and provide a detailed steps:
In the installation process, make your application to the .NET Framework 1.0 Shooting Web application to a specific .NET framework to get the .NET framework version of the Web site, usually, when the components or applications on a computer are upgraded, the old Version components or applications are replaced by the new version of components or applications. If the new version is not compatible with the old version, this often affects other applications that use the component or application. The .NET framework performs support, which allows multiple versions of an application to be installed on the same computer simultaneously. Because multiple versions can be installed at the same time, the controlled application can choose which version uses and does not affect the application of other versions.
During the installation of .NET Frame 1.1, all existing ASP.NET applications are automatically reconfigured to use the latest version of the .NET framework. If you don't want your ASP.NET app being configured to run .NET Framework 1.1, click
Learn how to avoid it during the installation process.
If you upgrade the web server to the .NET framework 1.1 and want one or more applications to run .NET Framework 1.0, you need to update the Internet information service script mapping. Script mapping is a mechanism to extends the name of the .aspx file of a particular application to a .NET framework. Click
Here is to understand how to shoot a web application to a specific version .NET framework.
Using the Internet Information Manager or ASP.NET IIS Registration Tool (ASPNET_REGIIS.exe), you can know the .NET framework version used by a particular web application. Click
Here is to understand how to confirm the version of the .NET framework that is currently running in a Web site.
When migrating to the .NET framework 1.1, it is important to consider a very important thing that each version of the .NET framework uses the different Machine.config files. Therefore, if the web administrator has modified to Machine.config, you must do the same modification in the .NET Framework 1.1 Machine.Config.
Map your application to .NET framework 1.0 during installation
During the installation of .NET Frame 1.1, all existing ASP.NET applications are automatically reconfigured to use the latest version of the .NET framework. Use the new version of the .NET framework, the application gets all enhanced performance and new features built into the new version. At the same time, for the WEB administrator who wants to be meticulous to control, he can prevent the existing ASP.NET application from re-mapping during the .NET framework.
To prevent all ASP.NET applications from being rereaded to the new version of the .NET framework, the web administrator can use the / noaspupgrade command line option when running the DotNetfx.exe installer.
Fully prevent ASP.NET applications from re-maping to the new version
Open Start Click Run Enter CMD Click OK to Enter the next line in the command prompt: DOTNETFX.EXE / C: "Install / noaspupgrade". Click Yes in Microsoft .NET Framework 1.1 Setup. Start .NET Framework 1.1 Install the process.
Image web application to a specific .NET framework
Each version of the .NET framework contains an ASP.NET IIS Registration Tool (ASPNET_REGIIS.exe). This tool enables administrators to specify a web application running under a specific version .NET framework. This is called a mapping web application to the .NET framework. The administrator must select the corresponding ASPNET_REGIIS.exe that is associated with the web application. For example, an administrator wants to specify the Web site to use the .NET framework 1.1, he must use ASPNET_REGIIS.exe from the .NET framework 1.1.
1.0 version of ASPNET_REGIIS.EXE is located in: c: /windows/microsoft.net/framework/v1.0.3705/ASPNET_REGIIS 1.exe in:
C: /Windows/Microsoft.net/framework/v1.1.4322/ASPNET_REGIIS ASPNET_REGIIS.EXE provides two options for script mapping web applications
-S For the current path and its sub-path setting script mapping - SN only sets only the web application IIS metadata path for the current path, and the metadata path is defined as such format: W3SVC / ROOT / {Websitenumber} / { Application_name}. For example, a metadata path for web applications in the default Web site is W3SVC / 1 / Root / Portal.
Note that you can also use a tool named Metabase Editor to get the metadata path. You can download this tool in Microsoft Support Site
http://support.microsoft.com/default.aspx?scid=kb;n-us;232068 "
Run an ASPNET_REGIIS.EXE -S W3SVC / 1 / Root / Portal update Portal and its subroutine IIS script mapping.
Run the ASPNET_REGIIS.EXE -SN W3SVC / 1 / Root / Portal update Portal's IIS script map without affecting applications in its subdirectory.
Get the .NET framework version used by the Web site
Administrators can use the Internet Service Manager to get the .NET framework version of the Web site. Internet service manager running different operating systems is different. To run the service manager, follow the steps below:
Start Internet Service Manager
Open start. Click Run. Enter inetmgr. In the Internet Service Manager, select the web application you want to know. Net Framework version of the web application right-click Application, click Properties. Select Configure Configure in the Application tab in the Properties window, select .aspx, click Edit. After the text box after executable is scrolling, look at the version directory. If the text directory is v.1.1.4322, the application is mapped to the .NET Framework 1.1, which is reversed, if the version directory is V1.0.3705, the application is mapped to the .NET framework 1.0.
