When will we be able to use remotely under different host?

bluebsh · Post by **bluebsh** » Thu Sep 20, 2007 11:38 am

This is still a MAJOR issue for us... internally our source control is called "sourcecontrol" for the DNS Alias... externally its on our "intranet" public host... we can not open source control items anymore (as ive stated a few months ago) from outside the building! and making a host record on our local system does not fix the problem... since it forwards that host name to our IIS server which then reads it as an invalid host header for what ever reason... (our vault service listens on port 80 on by host headers looking for "sourcecontrol" but when it comes from outside in it doesnt want to work since somehow it still comes from "intranet" which it doesnt like)

but WHEN do we plan on having this fixed? it worked all through version 3 but when version 4 came out it no longer worked...

Beth · Post by **Beth** » Thu Sep 20, 2007 3:25 pm

Which VS IDE interface are you using? Did you end up making the switch to VSIP (VS 2005 client)?

bluebsh · Post by **bluebsh** » Mon Sep 24, 2007 12:44 pm

We are using Visual Studio 2005 Pro SP1 and the VS2005 IDE Plug-in. This problem did not happen in the VS2003 Vault IDE Plug-in.

Beth · Post by **Beth** » Mon Sep 24, 2007 3:18 pm

A bug had been logged on that issue. A fix will be written for a future release. It won't be done in time for 4.0.5. Developers are actively working on that one though, so it is still coming.

The only work-around for this issue currently is to use the MCSCCI client (VS 2003 compatible client) instead of VSIP (VS 2005 client). On the projects that external users need, you may wish to consider switching those projects to MCSCCI. That would mean users unbinding, changing the setting to VS 2003 and then rebinding the projects.