Hello,
All my devs including me work from home offices. Internally I use Vault 1-user free license for my internal work, then we have a 5-user vault license which is on our shared server for our team development. I'd like to take a look at Fortress to see what it has to offer and take advantage of the single-user free license.
If I install Fortress on my machine and internal server, will I still be able to use Vault on our shared server connecting from my machine with Fortress installed? How will this "mixed" environment be handled?
Mixing Vault and Fortress?
Moderator: SourceGear
Mixing Vault and Fortress?
Neal Culiner
NC Software, Inc.
http://www.nc-software.com
Vault 5.1.2
VS 2010/C#
Windows 7 Ultimate x64
VB.NET Forums: http://www.vbdotnetforums.com
NC Software, Inc.
http://www.nc-software.com
Vault 5.1.2
VS 2010/C#
Windows 7 Ultimate x64
VB.NET Forums: http://www.vbdotnetforums.com
Vault Server and Fortress Server cannot be installed on the same server machine.
You can install Vault Client and Fortress Client on the same machine. The main thing I've noticed about having them both on the same machine is that in Visual Studio 2005, you usually have to reset the SourceControl provider, as it tends to try to use the source control provider last accessed.
For instance if you've been logged into Fortress, then you close and reopen Visual Studio and try to log into a Vault Server, you may get an error that this protocol is not supported. Cancel out of the connection dialog and go into VS and change the source control plugin in Tools->Options->Source Control to Vault.
You can install Vault Client and Fortress Client on the same machine. The main thing I've noticed about having them both on the same machine is that in Visual Studio 2005, you usually have to reset the SourceControl provider, as it tends to try to use the source control provider last accessed.
For instance if you've been logged into Fortress, then you close and reopen Visual Studio and try to log into a Vault Server, you may get an error that this protocol is not supported. Cancel out of the connection dialog and go into VS and change the source control plugin in Tools->Options->Source Control to Vault.
Linda Bauer
SourceGear
Technical Support Manager
SourceGear
Technical Support Manager