Hi,
I can connect to Vault using the VaultGUI using the address in this form: <servername>.<company>.local/VaultService.
Furthermore I can use Visual Studio Enhanced plugin to 'Open from Vault' from the same address.
However, if I open a solution that way it is still offline in Visual Studio. When I try 'Vault -> Go Online' it insists on connecting to
<servername>/VaultService.
Notice how ".<company>.local" is missing here.
The result is the well known error "Unable to connect..."
Trying this in Firefox yields the same results: <servername>.<company>.local/vaultservice works, but <servername>/vaultservice does not work.
How do I make clear to the VS plugin that it should connect to the fully qualified name?
We're using Vault Client 4.1.3 here.
Thanks for any help,
Christiaan
Unable to connect in Visual Studio, Gui works fine
Moderator: SourceGear
-
- Posts: 2
- Joined: Thu Jul 16, 2009 1:27 am
Re: Unable to connect in Visual Studio, Gui works fine
There may be some useful suggestions in this related forum post:
http://support.sourcegear.com/viewtopic ... 94&p=44972
http://support.sourcegear.com/viewtopic ... 94&p=44972
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager
-
- Posts: 2
- Joined: Thu Jul 16, 2009 1:27 am
Re: Unable to connect in Visual Studio, Gui works fine
Thank you. I thought I had seen all possibly related posts before entering my own. But I missed this one.
Indeed I solved it by an entry in the hosts file.
Solving it in the solution file is not a viable option for me, since the bare servername is perfectly ok for the company's own developers. Just for me the servername should be fully specified.
I hope that you can fix it in version 5. For example, make it configurable and store it in the .suo file. That is not checked in nor shared with the other developers.
Indeed I solved it by an entry in the hosts file.
Solving it in the solution file is not a viable option for me, since the bare servername is perfectly ok for the company's own developers. Just for me the servername should be fully specified.
I hope that you can fix it in version 5. For example, make it configurable and store it in the .suo file. That is not checked in nor shared with the other developers.
Re: Unable to connect in Visual Studio, Gui works fine
I've logged feature request 14668 to improve this functionality.
It won't make it into Vault 5.0, however, since it's already feature-complete and scheduled to be released soon.
It won't make it into Vault 5.0, however, since it's already feature-complete and scheduled to be released soon.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager