We have a VS 2003 solution that consists of several ASP.NET web service project (and, no, we aren't in a position to upgrade to VS 2005/2008). Currently, the local paths for the web service projects all point to WWWRoot. I figured this will be a problem w.r.t. branching and I’m wondering if there’s any way to configure things so that the web service project’s local paths are relative to the solution’s root rather than relative to WWWRoot. I thought I could work around this by remapping the IIS virtual directories so that they point at the solution’s root. I then hand-edited the .sln file and adjusted the project paths. From an IIS perspective this works fine but VS 2003 doesn’t like it at all. When I “open from source control”, it pops-up a dialog that asks me to set the local folder for each of the web service projects and insists that I set it to something relative to //localhost then complains that it can’t open the project. If I “get latest” and open from the local mapping, it complains that the projects are not under source code control (since the MSCCI provider file is missing).
Does anyone have a workaround for this?