How to Configure Different Versions of an ASP.NET Application Running on the Same Web Server
Here is an excerpt from the KB article: KB 816782 Find the ASP.NET Version Used for the Application View the script map for an ASP.NET application to determine the version of ASP.NET that the application uses. To view the script map for an ASP.NET application, follow these steps: Click Start, point to Programs, and then click Control Panel. Double-click Administrative Tools, and then double-click Internet Information Services (IIS). Expand local computer, expand Web Site, and then expand Default Web Site. Locate the folder that contains the ASP.NET application. Right-click the folder that contains the ASP.NET application, and then click Properties. Click the Directory tab, and then click Configuration. The Application Configuration dialog box opens. Click the Mappings tab, and then select an ASP.NET application extension, such as .asmx or .aspx. The Executable Path column of the dialog box lists the path to the ASP.NET ISAPI version that the application uses. By default, the ASP.NET ISAPI is installed in %WindowsDirectory%\Microsoft.NET\Framework\%versionNumber%. The version number in the path indicates the version number of the ASP.NET ISAPI that the application uses. The ASP.NET ISAPI version determines the version of the runtime that the application uses. Use Aspnet_regiis.exe to Update the Script Map To make it easier to reconfigure the script map for an ASP.NET application, each installation of the .NET Framework is associated with a version of the ASP.NET IIS Registration tool (Aspnet_regiis.exe). You can use this tool to remap an ASP.NET application to the ASP.NET ISAPI version associated with the tool. Note Because Aspnet_regiis.exe is linked to a specific version of the .NET Framework, you must use the appropriate version of Aspnet_regiis.exe to reconfigure the script map for an ASP.NET application. Aspnet_regiis.exe only reconfigures the script map of an ASP.NET application to the ASP.NET ISAPI version associated with the tool Configure ASP.NET 1.0 for the Application When ASP.NET 1.1 is configured on the root Web site, follow these steps to configure ASP.NET 1.0 for an application: Click Start, and then click Run. In the Open text box, type cmd, and then click OK. At the command prompt, locate the following directory path: %WindowsDirectory%\Microsoft.NET\Framework\v1.0.3705\ Type the following command to configure the ASP.NET 1.0 application in IIS: aspnet_regiis -s w3svc/1/root/ApplicationName To remove ASP.NET 1.0 from this application, repeat steps 1and 2, and then type the following command: aspnet_regiis -k w3svc/1/root/ApplicationName Configure ASP.NET 1.1 for the Application When ASP.NET 1.0 is configured on the root Web site, follow these steps to configure ASP.NET 1.1 to run an application: Click Start, and then click Run. In the Open text box, type cmd, and then click OK. At the command prompt, locate the following directory path: %WindowsDirectory%\Microsoft.NET\Framework\v1.1.4322 If ASP.NET 1.1 is not already registered, type the following command to register it: aspnet_regiis -ir Note The -ir option registers ASP.NET 1.1 without updating the scripts in IIS. Type the following to configure the ASP.NET 1.1 application in IIS: aspnet_regiis -s w3svc/1/root/ApplicationName To remove ASP.NET 1.1 from this application, repeat steps 1 and 2, and then type the following command: aspnet_regiis -k w3svc/1/root/ApplicationName
Why do I get the error message ‘Server Application Unavailable The web application you are attempting to access on this web server is currently unavailable. Please hit the ‘Refresh’ button in your web browser to retry your request.’
By default, ASP.NET runs its worker process (Aspnet_wp.exe) with a weak account (the local machine account, which is named ASPNET) to provide a more secure environment. On a domain controller or on a backup domain controller, all user accounts are domain accounts and are not local machine accounts. Therefore, Aspnet_wp.exe fails to start because it cannot find a local account named ‘localmachinename\ASPNET’. To provide a valid user account on the domain controller, you must specify an explicit account in the section of the Machine.config file, or you must use the SYSTEM account. For more details : FIX: ASP.NET Does Not Work with the Default ASPNET Account on a Domain Controller
Why do I get ‘HTTP 500’ error (or ‘(DLL) initialization routine failed’) in my browser?
This is because if you have the /3GB boot switch enabled, the ASP.NET worker process (Aspnet_wp.exe) does not start. For more information see Microsoft Knowledge Base Article – 320353 To create and set the ‘ASPNETENABLE3GB’ environment variable as mentioned in the above article, right click MyComputer ->Properties->Advanced > Environment Variables > System variables > New. Add the variable name in the top text box and the value in the lower textbox.
How To Repair ASP.Net IIS Mapping After You Remove and Reinstall IIS?
To reassociate aspx file extensions with ASP.Net runtime, you’ll have to run the utility aspnet_regiis.exe -i For more information refer to Microsoft Knowledge Base Article – 306005
Why did my request hang after I switch to SQLServer mode
(Right answer?) Refer What kind of objects can I store in Session State?