Does Vault 7.0 Fix the offsite vs. onsite host name issue?

[Mordachai]

I've asked this, and I've seen others ask this frequently:

Onsite, the vault server is known locally as "build-server"
Offsite, the vault server is known as "build-server.ourcompany.dns2go.com"

Sadly, Vault's bindings interact with VisualStudio in such a way that the two are incompatible, and error offsite.

i.e. I cannot (nor can anyone) find a way to make bindings for VisualStudio projects that work correctly when the project is accessed through a different URL. Same server, same project, different host-path.

[Beth]

Can internal users reach build-server.ourcompany.dns2go.com?

[Mordachai]

Nope. Only external ones.

We're behind a NAT router, and use dynamic DNS to offer access to certain services (e.g. Vault). But the external name and internal name cannot be the same.

[Beth]

Is there an IP address that both locations can reach?

What you might consider trying is setting up the hosts file to resolve the name to the appropriate IP address, then each client would have their hosts file configured differently, but still use the same name in binding Vault.

[Mordachai]

This would work if the IP address didn't change.

But I tried this in the past - and the dynamic IP address does change (about weekly). So it's just not worth it.

If I could create an alias DNS binding on local machine, that would work... but alas, this is not possible, nay?

Which is why - for this to ever really work - I do believe it will have to be supported by Vault natively (some sort of server_alias= binding reference for each project? Or an alias configuration for the client itself?)

[Beth]

Were you able to do this previously with Visual SourceSafe? If so, then you might try the Vault Classic Client instead of the Vault Enhanced Client. The Classic Client uses the same API that VSS did.

[Mordachai]

We used your excellent SoS product.
I believe that handled things correctly - i.e. it used a server URL in its configuration that worked. Not sure if the VS environment worked with it automatically, or if check outs had to be done manually. Manually, I think. Similar issue.

[Beth]

SOS also uses the same Visual Studio API that VSS uses and the Vault Classic Client uses.

I have instructions posted, http://support.sourcegear.com/viewtopic ... 13&t=18956, for how to rebind to the Vault Classic Client posted if you want to give that a try.