How to Change the Vault url

[btd]

When I launch Visual Studio 2008 and try and open my solution file, I get prompted with a Vault login splash screen (see attached).

As can be seen from the attached file, the Vault URL is not fully qualified. And since the computer I am trying to launch Vault from is in a different domain, I need to change the url to this
Connecting to http://fhlbcinapp1.myDomain.com/VaultService

Question: How do I do that?

Note: We are running version 5_1_1_19215.

Also note: If I open a browser and usew the Fully Qualified Domain Name, I am able to connect to Vault.

Thanks

BTD

[Beth]

The entire solution needs to be unbound from its current bindings and bound to the FQDN.

There is a KB article that can help you with the rebinding posted here, http://support.sourcegear.com/viewtopic ... 13&t=18956, with one change to it. To choose a different server path, you need to close Visual Studio entirely in between unbinding from the previous path and rebinding to a new path.

[btd]

Beth:

I'm confused and looked at that link but it refers to topics with VS2003 and VS2005. I am using VS2008.
Can you tell me wHich topic in the KB addreses the fix?

[Beth]

What you saw about VS 2003/2005 and just the old names of the clients. The instructions are exactly the same for VS 2008.

If you are using the Vault Enhanced Client, try these instructions here: http://support.sourcegear.com/viewtopic ... 342#p68342 (just a portion of that first KB article).

Or, another good article that may help is posted here: http://support.sourcegear.com/viewtopic ... 487#p68487. It talks about unbinding first, and then returning to the binding dialog to rebind. In your case, you need to close and reopen Visual Studio so that you can select a different server name.

Essentially, you need to get the project open, get it unbound through the Change Bindings dialog, then close and reopen VS, and bind it through the same Change Bindings dialog windows.

If things aren't lining up with what you are seeing, then send an email to support at sourcegear.com (attn: Beth) with a link to this forum thread and we can go through this.