7

My employer recently upgraded us from VS 2010 to VS 2012. It's been great, but there is one minor annoyance that I'm hoping someone here can help with. In VS 2010 when I switched branches it would ask me whether I wanted to update the IIS paths. Something along the lines of "the path for port:blah is pointing here. Would you like to change it?" VS 2012 doesn't bother asking. It just changes it. I can't seem to find a setting that discourages this behavior, so I'm hoping someone else out there has. Searching IIS on any site brings up way too many results to sift through, especially considering that only one (a topic from this forum, actually) of the first thirty or so had anything to do with IIS and Visual Studio updating the paths (sadly not related to this issue). Any help would be much appreciated.

EDIT: I found the exact message. It reads: "The Web project '...' is currently configured to use the URL '...'. The Web server has this URL mapped to a different folder '...'. Would you like to remap this URL to point to this Web project's folder?"

Kerfuffle
  • 176
  • 11
  • Has no one else run into this issue? I'm still trying to find an answer, but no luck. If anyone else finds it, please post it here. – Kerfuffle Mar 18 '13 at 14:55
  • I am having this exact same issue. The answer submitted doesn't look like much of an answer. Has there been any additional solution for this? – Scottie Apr 05 '13 at 18:36
  • Sadly, no. Their response is basically "This cannot be done.". It's annoying, but there you have it. – Kerfuffle Apr 07 '13 at 18:32
  • This is definitely an annoyance with VS 2012. Has anyone found a solution or workaround? – UT-Fan-05 May 20 '13 at 15:26
  • Yes, this is a really annoying issue that's been bugging me as well. For myself, one of my branches doesn't need to be mapped to an IIS application at all. I simply want to make sure it will compile before checking in. It's very tedious having to either manually update the physical path in IIS or restart VS. I didn't find this question at first, and was about to ask this same question until I found this. – Itison Sep 11 '13 at 00:54
  • 1
    @Itison: if for compile check, you can just use this cmd: `msbuild /P:Config=Debug` It'll be faster than open it in VS 2012 – Dio Phung Mar 27 '14 at 03:58

2 Answers2

3

I took this question to the MSDN forums. I received an answer there so I am just linking this question to the MSDN question.

MSDN forum question

Request on visualstudio.uservoice.com

J c
  • 6,387
  • 3
  • 29
  • 29
Kerfuffle
  • 176
  • 11
1

Just my work around for this problem:

  • In IIS Manager, I created Sites for each branch, then I configured them using different Ports.

  • Open each of the web projects in VS2012, then set the properties as:

    • Start Action = Don't open a page. Wait for request from external application.

    • Servers = Local IIS

    • Project URL: http://localhost:[PORT for this site on IIS]

This way, VS2012 will not modify the web port & path. I can still debug with different branches.

Is that helping you ?

Dio Phung
  • 5,944
  • 5
  • 37
  • 55