Disabling source control integration completely
Is there any easy way to disable source control integration in VS2005, even for projects that have source control associations? For example, I have a project that's bound to a VSS project. I would like VS to open the project as if it had no source control association. I tried changing the selected source control provider in Tools/Options to "None", but when I open a project bound to VSS, it changes back to "Microsoft Visual SourceSafe".
The use-case here is that we have some remote developers that can't use integrated source control, and some local developers that can. If the local developers bind the project to source control, then the remote developers want to be able to tell VS to ignore the binding and manage the checkins manually, outside of the IDE.
Hi Kevin,
If the remote developpers don't have VSS installed at all on their machines, when they will open a VSS-controlled solution they should get prompted with a dialog
Source Control - Unable to Access Database
The associated source control plug-in is not installed or could not be initialized.
Temporarily work uncontrolled / Permanently remove source control association bindings
They could click "Temporarily work uncontrolled" and work on the files in the project (but they should make sure not to change the project and solution files, as this may disable scc integration for other users)
If the remote developpers have installed VSS but they cannnot use integrated source control because the database is not available, they will be prompted to switch to "VSS Internet" provider and if the switch is not allowed or if connection is still not possible by using Internet plug-in then they will be prompted again to "Temporarily work uncontrolled"
Alin
They do have VSS installed on their machines, they just don't want to use source control integration in the IDE. At all. Having to answer a prompt every time they open a project is a major drag.
Is there really no way to just disable it, period? To ignore the binding information in the project, but don't remove it?
Let me make sure I understand, you want some people (those in your office) to have the project bound and working under source control; but other users (the remote ones) to work on exactly the same project/solution as if it was not under source control, right?
If that is the case, then the answer is indeed No.
The best alternative is what Vince suggests: Have those who are offsite do File->Source Control->Change Source Control and disconnect their project. They will still see the files under source contol, but will be able to work with them, and will not get prompted every time they open the project.
