Proxy Problems

thaoula · Post by **thaoula** » Wed Jan 11, 2006 3:01 pm

Hi Guys,

I have a problem configuring proxy settings for use with Vault. At work we use an autoconfiguration script to configure the proxy. I understand this does not work in Vault due to a bug in .Net.

I have followed the instructions for setting proxy settings in the vault configuration file. The vault client is now able to connect to local vault servers and vault servers through a proxy without constant modification of the proxy settings.

However, the VS 2005 IDE does not seem to use the settings specified in the Vault config file. It requires the settings to be specified in manually in the Vault client.

Is it possible to specify proxy settings for the VS 2005 IDE?
Why dont you make the proxy settings part of the profile?
Can you add a bypass local to the proxy configuration?

Your assistance is appreciated.

Kind Regards,
tarek

lbauer · Post by **lbauer** » Wed Jan 11, 2006 4:14 pm

However, the VS 2005 IDE does not seem to use the settings specified in the Vault config file. It requires the settings to be specified in manually in the Vault client.

Thanks for the info; I'll check into this. Visual Studio may just use the registry settings that are set by the GUI Client options.

If I understand your post correctly, you'd like to be able to be able to configure proxy settings specifically in Visual Studio, rather than have do to this in the Vault Client? And you'll like to be able to do it in the profile?

I'll log this as a feature request.

thaoula · Post by **thaoula** » Wed Jan 11, 2006 4:25 pm

Hi Linda,

I appreciate your prompt response to this issue.

Essentially, VS 2005 does not seem to use the proxy settings configured in the Vault Client.exe.config.

I need to access a local vault server and a remote server. If i configure a proxy server in Vault Client, i can use VS 2005 to access the remote server but i cannot access the local server. If i dont configure a proxy server i can access the local server but not the remote. This issue is compounded by the need to access the local and remote servers at the same time (using to instances of VS)

It would be usefull to specify proxy settings per profile. Otherwise Vault should allow for a bypass local settings in the Client. It is currently available only in the config file.

Kind Regards,
Tarek

thaoula · Post by **thaoula** » Mon Jan 16, 2006 3:13 pm

Hi Linda,

Can you please advise what Sourgear's position is on this issue as it makes working on multiple projects extremely difficult.

Kind Regards,
Tarek

lbauer · Post by **lbauer** » Mon Jan 16, 2006 5:59 pm

I've logged a feature request for proxy configuration to be added to the login profile. In the meantime, we'll see if there's any workaround to this problem and post back here.

dan · Post by **dan** » Tue Jan 17, 2006 2:43 pm

One workaround might be to specify the proxy in the devenv.exe.config file, located in the same folder as VaultGUI.exe.config. VS 2005 might load those settings instead of the GUI client ones.

However, I've been playing around with this in 3.1.6, and can't get the .config file settings to take effect anywhere, because the GUI client options is only changing the registry settings (at HKCU\Software\SourceGear\Vault\Client\Settings) rather than the .config files. So, you might try updating the registry too.

Unfortunately, the registry doesn't have a bypasslocal option. As Linda mentioned, we'll add that as a todo item too, but in the meantime, playing with the registry and the devenv.exe.config file might produce a workaround for you.

thaoula · Post by **thaoula** » Wed Feb 08, 2006 4:25 pm

Hi,

Can you please advise when this feature request will be implemented?

This is becoming a real problem.

Kind Regards,
Tarek

dan · Post by **dan** » Wed Feb 08, 2006 4:39 pm

We don't have a release date for this issue yet.

We recently had another issue with a configuration problem in VS2005, and it was traced back to needing to edit the devenv.exe.config file that is in the VS2005 install folder (C:\Program Files\Microsoft Visual Studio 8\Common7\IDE), rather than the one in the Vault install folder. Try making the proxy changes there (and removing the registry settings) and see if that helps.