ASP.NET
Cool stuff in ASP.NET, IIS Problems & Solutions etc.
I installed the .NET Passport 2.5 SDK, to enable SSI on one of the portals I am developing. One good thing about version 2.5 of the SDK is that it has support for managed development in C#. I wanted to host this portal on my ASPXConnection webspace. Unfortunately ASPXConnection doesnt give access to some resources which may be required in special cases such as this. To install the Symmetric Key given by the Passport Services Manager, I needed command line accees to install the key. :-(
I had installed the .NET Passport 2.5 SDK on my system and uninstalled the same after realizing that I would not be able to do this with my webspace. The next time hit F5 in VS.NET 2003 to run my web application, it said:
“Unable to start debugging on webserver”
I run the web application without debugging and it was ok. Conclusion was that my Web.config was ok. I didnt want to research for a very long time on this issue, so went ahead with the good old “KB306160”. I reinstalled the .NET Framework and everything was back to normal.
Update: Article 306172 seems to be a better place to start off, if you have ASP.NET & IIS issues
Quite a few times I have faced the problem of running ASP.NET web applications on my IIS.
The various errors which I used to get are:
- “Cannot start ATL or COM debugging“
- “The webserver running your web application is in the Internet Zone“
- “Cannot start ASP.NET debugging on this webserver“
Every time I did a search for help on these topics, I landed on the respective Microsoft Knowledge Base Articles, which explain these problems in a nice manner. One such article is “Visual Studio .NET has detected Web server is not running ASP.NET 1.1”.
The problem with my IIS was this one:
3. Web Server specified by ASP.NET Web Project/Web Service Project is stopped or IP address cannot be mapped.
A: Please check IIS's Web configuration, include IP Address and working status. If your network IP address already changed, you must change your Web Site's IP Address. (If you use "localhost" to create Web Project, you can do nothing.)
All I did was changed the IP address configuration in IIS to 127.0.0.1. I did try to use localhost, but IIS doesnt take it. Once I did this, I was able to create ASP.NET applications. The next problem was that I wasnt able to run the ASP.NET web application because the URL of the web application ie. http://127.0.0.1/WebApp1 was in the InternetZone. The solution for this is given in the MSDN Library.
Tough these are some small issues, it would be a real pain if one does not know that the MSDN KB has solutions for all these.