.NET Framework 2.0 (CodeName: Whidbey) is the buzz word around and most of us would have installed the BETA versions to try our hands.
However, after you install .NET Framework 2.0, if you continue to use Visual Studio.NET 2003 you may be unable to debug the applications developed in .NET 1.1. You may receive the error "Unable to start debugging on the webserver..."
The reason is, as a part of installation, the framework registers the 2.0 version with the IIS using the aspnet_regiis.exe -i utility and the script mappings for the virtual directories get updated to 2.0 version.
Therefore, debugging .net 1.1 applications may fail.
The Resolution for this is to change the script mappings in the IIS - virtual directory settings for the application.
Once you install .NET Framework 2.0, you will be able to find the ASP.NET Tab in the Virtual Directory Properties in IIS.
The following steps provide resolution.
1. Type inetmgr from your command prompt
2. Expand the relevant nodes to select your Virtual Directory.
3. Right Click on the virtual directory and select properties.
4. You will be able to see the ASP.NET Tab which has newly come up.
5. Click on the ASP.NET tab.
6. You will be able to see a Dropdownlist with .NET 2.0 and .NET 1.1 versions listed.
7. Select the 1.1 Version and click Apply and then click ok
Now you will be able to debug your applications developed in .NET 1.1 using Visual Studio.NET 2003.
There are other errors that you may receive when running .net 1.1 applications after installing .NET 2.0. which I will explain in next article.
Happy Programming!
posted @ Monday, April 25, 2005 7:54 AM