VS client always want to connect to local repository

[Pat123]

Hi,

Have installed vault and added a vs2008 solution on one computer and everything is working fine on that.

On a second computer, I installed vault client, fired up vs08 and selected 'add from vault'.. found the repository ok at the remote location and was able to download the solution and all seemed ok. However, after restarting vs08 and re-opening the solution, I have to choose the option 'go online', and when I do that vault always brings up the login dialog saying 'connecting to http://127.0.0.1/VaultService', rather than the real location of the repository. If I run the standalone vault client, it connects to the correct location by default.

What is going wrong? Is this the correct way to setup a solution from vault on a second computer?

[Beth]

Did the first client or the second client place the full solution into Vault? Normally, the first client puts the entire solution in. Assuming that's the case, then the second client, would first need to make sure the same client is set in VS Tools - Options - Source Control, and then use the function Open From Vault or Open From Source Control and not the Add function.

[Pat123]

The first client placed the entire solution in. I am trying to setup the second client to use/download the solution from the remote repositary created by the first client.

Sorry, I meant 'open from vault' when I said 'add'. After I 'open from vault' on the second client, it connected to the remote repositary and everything downloaded as expected. However, after I closed and re-opened the new solution and 'go online' to connect to the remote repositary again, the login prompt appears and is always trying to connect to http://127.0.0.1/VaultService/ rather than the remote repositary address. Both clients are using the Enhanced client. The standalone vault client connects to the remote repositary fine.

[Pat123]

This is the setup on the second client that I want to connect to the remote server:

Client Information
Vault Client Version: 4.1.4.18402
.Net Framework Version: 2.0.50727.3053
Operating System: Microsoft® Windows Vista™ Ultimate
Service Pack: 1.0
OS Version: 6.0.6001
Total Physical Memory: 2 GB
Time Zone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London

Server Information
Vault Server Version: 4.1.4.18402
.Net Framework Version: 2.0.50727.3074
Operating System: Microsoft® Windows Vista™ Ultimate
Service Pack: 1.0
OS Version: 6.0.6001
Timezone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London
SQL Version: Microsoft SQL Server 2005 - 9.00.4035.00 (Intel X86)
Nov 24 2008 13:01:59
Copyright (c) 1988-2005 Microsoft Corporation
Express Edition on Windows NT 6.0 (Build 6001: Service Pack 1)

License Information
0 serial number(s):

[Beth]

When the first client placed the solution in, was that client on the server machine or remote from the server?

I'd like you to try unbinding and rebinding to see if you can get bound to the correct IP. With your solution open, go to File - Vault Source Control - Change Vault Bindings. Select everything and click unbind. Then click OK and perform a Save All. Then return to File - Vault Source Control - Change Vault Bindings. Click on the line for the .sln and click Bind. You should need to login to Vault and browse to the folder containing the .sln. After you bind the .sln and receive see "valid" in the window, then bind the other lines, unless everything bound at once. Then click OK and perform a Save All.

Then let me know your results.

[Pat123]

There were some settings in the solution file, 'VaultHost' and 'SCCAuxFile' set to connect to localhost. This must have been brought over when I downloaded the solution from the repository. I manually changed the settings and it works now. If I want to have keep solution file in the repositary is there a way around this?

[Beth]

When you place your solution into Vault, you might use the server name or IP instead of local host.

[Pat123]

Thanks, that worked.

[Beth]

Thanks for the update.