No VS integration on purpose, anyone?

This forum is now locked, since Gold Support is no longer offered.

Moderator: SourceGear

Posts: 288
Joined: Wed Dec 22, 2004 11:10 am

No VS integration on purpose, anyone?

Post by Tri » Mon Feb 28, 2005 1:31 pm


A developer in our team has had enough of all the VS2003 integration troubles (mostly non-reliable get latest, check in sometimes acted as undo checkout). He has decided to work with no VS integration. He does all source control operations via Vault client (2.06).

Did any of you have a similar situation where a developer in your team disables VS integration on purpose?

Posts: 3660
Joined: Tue Dec 16, 2003 1:17 pm
Location: SourceGear

Post by jclausius » Mon Feb 28, 2005 2:14 pm

I'm not sure this is supported with VS.Net, but I've run a couple of different projects in similar situations. No real problems to report.

If you run projects with Vault enabled, and another user has NO SCC provider, they will get some error messageboxes in VS.Net, but once clicking throught them, the projects work fine.

If you run projects with Vault disabled, anyone wanting to use the integrated client has to create custom project files with the SCC enabled. The key is this user cannot make any changes to the project file unless they disable ALL of the SCC related stuff from the project file.

Are there any specific question you may have?
Jeff Clausius