Automated Build Process

[Cullen Waters]

2 questions, please.

Background:
We are finally getting to set up an automated build box, to perform nightly builds of our core product. We ran into a couple of issues, and I'd appreciate some clarification.

1. We tried to use SOS to access our repository, but ran into trouble using an existing user name. Do we need a seperate license for SOS, just for the build box? No one will be doing any work on that box, it is completely automated, and just ftp's our build outputs.

2. When using VSS to connect to the database, we found that our .sln file was corrupted. Is there any known issue with using SOS and VSS to access the same db? We all use SOS to connect, because we have laptops and are mobile, but the build box is on the same network as our VSS server, so we set up VSS, after running into trouble using SOS(See #1). Should that cause any problems?

[Edit]
3. Is it possible to use the command line client to refresh the project tree?

Thanks for the replies.

[lbauer]

1. We tried to use SOS to access our repository, but ran into trouble using an existing user name. Do we need a seperate license for SOS, just for the build box?

Every user that connects to the VSS database through the SOS Server needs an SOS license. Some users use an existing username or buy an extra license for "Build." What kind of problem did you have using an existing user?

2. When using VSS to connect to the database, we found that our .sln file was corrupted. Is there any known issue with using SOS and VSS to access the same db?

In what way was the file was corrupted? There can be issues with using both VSS and SOS with Visual Studio integration. See this KB article for details:http://support.sourcegear.com/viewtopic.php?t=1149

3. Is it possible to use the command line client to refresh the project tree?

In SOS 4.1, the GetProject command also refreshes the project tree.