In our development setup we use a remote VSS server and access it using the VSS Remoting tool from http://www.sourceremoting.com/ by providing the IP address and DB name to point to the correct VSS DB. We would like to use VSoft Technologies FinalBuilder 5 for automating our build process. We want to get latest code from the remote VSS location and build it using FinalBuilder tools. FinalBuilder expects the path to the srcsafe.ini file of the VSS repository. Our FinalBuilder script works fine when we get the latest code out of a VSS server on our LAN. We can configure the path to srcsafe.ini file as \\Options>FinalBuilder>Source Control Options>Default Source control provider" we are able to choose "VSS Remoting". However, it does not seem to have an option to provide details of a remote VSS; the IP address of the remote VSS server and VSS DB name like in the VSS Remoting tool.
Is it possible to access a remote VSS server through Final Builder?
There are two different source control access techniques in FinalBuilder. You can use actions (for example VSS Get Latest) to work on files as part of your build process (I think this is what you want.), or you can use SCC plugins to integrate with Source Control from inside the FinalBuilder IDE (similar to Visual Studio integration, this is only used to check the project you are working on in and out of version control.)
The option that you’re mentioning (Default Source Control Provider) only applies to the IDE Source Control integration (we’ll make this clearer in the options dialog.) You won’t actually see any prompt dialogs until you go to File -> Source Control -> Add Project to Source Control option in the IDE. This will tell the VSS Remoting plugin to add the FinalBuilder project to the repository, and it will hopefully prompt you for things like the Server and DB name.
However, I don’t think that’s what you want to do. If I’m not wrong, you want to use the VSS actions to get your source code files from the Remote VSS server. If so, you need the VSS actions. The VSS actions use the command line interface to VSS (SS.exe). I don’t know if the Source Remoting tool provides a compatible replacement for the SS.exe tool, but if it does then you should be able to select that tool under Tools -> Options -> Version Control Systems -> Visual Source Safe, and get the VSS actions to work that way.
If the command line tool is different, let us know and we may be able to provide you with another way to use it. I had a quick look at the Source Remoting web page but I couldnt’ see much in-depth technical info.