Microsoft Corporate Account
Visual Studio and .NET Framework Home
Cannot Use IIS Web Server option and set project URL in Visual Studio 2008 Professional
3/18/2008 10:22:06 AM
Primary Feedback Item:
User(s) can reproduce this bug
Having created a new Asp.Net Web Application on a networkshare in Visual Studio 2008 I cannot Use IIS Web Server option and set project URL, when this url targets a remote server.
Under "https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID=324664" I found a discussion which seems to target the same problem, but I cannot find a solution to my problem on this page, although the mentioned feedback has the status "closed(solved)".
Therefor I post this problem one more time.
Visual Studio 2008 (All Products and Editions)
Windows XP Professional
Operating System Language
Steps to Reproduce
Visual Studio 2008 Professional:
1) I create a new Website on a remote IIS (win 2003)
2) I can visit a webpage default.htm on this url
3) I connect to the mapped directory via a network share
4) and create a new Asp.net Web Application on this network share
5) I build the project with a demo page - ok.
6) Under Project > Properties > Web I select the option "Use IIS Web server" and under the textbox "Project Url" I enter the url from Step 2)
7) When I try to save this Project Settings, a msgbox with following text appears:
"The l o c a l IIS URL <url> specified for Web project <name> has not been configured. To keep these settings you need to configure the virtual directory. Would you like to create the virtual directory now?"
8) I can choose "yes" or "no", but in each case an error occurs. In case of "no" the message is:
"The l o c a l IIS server URL is not a valid URL or is not on the loval machine. The URL must incule a protocol (http:// or https://)."
9) The error here is, that vs 2008 just ignores, that I want to enter a URL for a r e m o t e server, not for the l o c a l machine!
With Visual Studio 2005 exactly these steps with exactly the same data function without any problem.
TAP Code (if applicable)
You can indicate your satisfaction with how Microsoft handled this issue by completing this quick
3 question survey
to post a comment.
Please enter a comment.
on 3/19/2008 at 2:23 AM
Thanks for your feedback.
We are escalating this issue to the appropriate group within the Visual Studio Product Team for triage and resolution.
These specialized experts will follow-up with your issue.
Visual Studio Product Team
to post a workaround.
Please enter a workaround.
on 4/10/2008 at 9:05 PM
Here is a workaround that worked for me:
VS will actually do remote debugging. It's just that it wants to check *locally* in the metabase (or equivalent in Vista/W28) first to be sure the site exists, which is a bug.
The workaround is to install IIS locally, then setup a local site with the same name as the remote site (just add a host header alias for the default local site). Use ping to be sure DNS is finding the remote site, not the local site.
Now the web section of the properties page will let you set the IIS option. From that point debugging works just fine!
© 2017 Microsoft