How to integrate Vault into an existing vs.net project?

rizzo · Post by **rizzo** » Mon Sep 27, 2004 11:31 am

Hello,

I have an existing very large vs.net 2003 project that is worked on by four people. Currently Vault is not integrated into the project. The way we do it is check out whatever file is needed via the Vault GUI Client and then work on it in the VS.NET 2003 IDE.

And that's the way other team members like it. I want to integrate Vault into my setup of vs.net 2003 without disturbing other team members.

How can I do this?

Thanks.

Post by **jclausius** » Mon Sep 27, 2004 12:04 pm

Rizzo:

It can be done, but I would NOT recommend this to anyone. Please use the following information at your own risk.

VS.Net places the SCC integration stuff within the project file(s). Once it has been added to a project file, VS.Net uses that information for the entire project.

Once a project has been bound, users who do not want SCC integration can "unset" Vault as their default Source Code Control provider. This can be done within the Vault client's options dialog.

Note, when a user who is NOT configured to use Vault as the SCC integrated provider opens a SCC bound project, VS.Net will complain with error dialogs, but once the dialogs have been closed, it still allows them to work.

As you can see, this scenario is a big pain.

Guest · Post by **Guest** » Mon Sep 27, 2004 12:15 pm

jclausius wrote:Rizzo:

It can be done, but I would NOT recommend this to anyone. Please use the following information at your own risk.

Note, when a user who is NOT configured to use Vault as the SCC integrated provider opens a SCC bound project, VS.Net will complain with error dialogs, but once the dialogs have been closed, it still allows them to work.
As you can see, this scenario is a big pain.

Ok, so other than the error dialogs, there won't be any reprocussions?
Also, how many error dialogs are we talking about?
And finally, exactly how can I bind an existing project to Vault?

Post by **jclausius** » Mon Sep 27, 2004 12:33 pm

Rizzo wrote:Ok, so other than the error dialogs, there won't be any reprocussions?
Also, how many error dialogs are we talking about?
And finally, exactly how can I bind an existing project to Vault?

Personally, I've never tried this situation. You may want to see if any of the VS.Net news groups contain any information regarding repercussions / error dialogs.

As for binding, just invoke the context menu on the solution or project (in a Vault enabled VSS), and then choose Add Project / Solution to Source Code Control. If you peruse around the Vault Knowledge Base, you should find more information in there.

HTH