Regarding a previous answer of yours that I have pasted below, I am sorry to say it is not working for me. My previous version is v1.0.3705 and new version is v1.14322. It is giving the same error: "Visual Studio .NET has detected that the specified Web server is not running ASP.NET Version 1.1. You will be unable to run ASP.NET Web applications or services." My OS is Win2k with a static IP.
By submitting your personal information, you agree that TechTarget and its partners may contact you regarding relevant content, products and special offers.
YOUR PREVIOUS ANSWER:
As of V1.0, there's a command-line utility to re-configure ASP.NET with all Web sites on your machine. You have to run the following command at the prompt:
Replace path with your current windows folder and .NET version. (The one I used is for v1.0.) That should do the trick.
Like I said in my answer, you have to replace the path with the appropriate one for v1.1 on your machine. And if you're using Win2k, the first folder is going to be WINNT and not WINDOWS: c:\WINNT\Microsoft.NET\Framework\v1.1.4322\aspnet_regiis.exe /i >[?There may have been an error while editing the content that caused the backslashes to be lost or misplaced (such as the //i).
You also need to have FrontPage Server Extensions installed and enabled in IIS to create a new Web application from VS.NET.
Another cause for the error is probably due to IE having a proxy configured. If FrontPage access is used to connect to the site, VS.NET may try to connect through the proxy, which will fail, of course. A reader reported that even if 'bypass for local addresses' is specified, VS.NET will ignore it.
Dig Deeper on ASP.NET development best practices
Related Q&A from Daniel Cazzulino
Here Daniel Cazzulino explains how to load a DSL (domain specific language) domain model instance file programmatically. This requires the .NET type ... Continue Reading
Here we offer a glimpse at 12 of .NET development expert Danny Cazzulino's top ASP.NET questions and answers. Continue Reading
C# developers should NOT be modifying InitializeComponent method in the code-behind (or any of the variable definitions) by hand. Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.