Binding An Existing Project/Soultion To VS.NET 2003

[Jerry Banasik]

Vault (Version 2.0.5.2210) has a problem setting up the integrated development environment (IDE) with Visual Studio .NET 2003 for an existing project or solution. If you are running Vault outside of VS.NET, everything works fine. Vault understands the tree structure and handles checking in and checking out files without a problem.

Before starting, have all developers check in all files and leave Vault closed until the VS.NET solution/project is correctly integrated on each developer's computer.

To set the Vault IDE for a VS.NET solution/project you do the following:
1) Make sure Vault is set as the source control provider. Do this by opening Vault and going to Tools > Options... > General and checking the Make Vault your default SCC Provider checkbox.
2) Make a backup copy of the solution/project files on the developer's computer and set it aside. Just in case something goes wrong!
3) Open your solution/project in VS.NET
4) Open File > Source Control > Change Source Control... to display the solution/project binding table.
5) Click on each Solution/Project item and click the Bind button

At this point you will see that each Server Name is underlined in red to indicate a problem with the binding.

6) Close VS.NET
7) Navigate to the root folder for each solution/project on your computer and open the MSSCCPRJ.SCC file in a text editor.
8) On the line that begins SCC_Project_Name = , complete the path to the folder that hold the MSSCCPRJ.SCC file. Vault leaves off the last folder in the path.
9) Save editing changes
10) Open VS.NET and the solution/project. Vault will prompt you to login during this process.

Now you will see that all of your files appear to be checked out. A look at the file properties (and Vault directly) shows that all files are really read only and checked in. Vault is just confused at this point.

11) Click on each solution/project in VS.NET, right click your mouse and select Check In...
12) On the popup tree view, make sure all files are selected and then click the Check In button.

At this point all files should be displaying a blue lock indicating Vault is back to normal.

Perform this operation for all developers.

[lbauer]

Was this project bound to a different SCC provider? If not, you should add the project to source code control:

http://support.sourcegear.com/viewtopic.php?t=776

This will create the proper bindings, etc.