Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

How to specify the source control plugin on a per-solution basis in Visual Studio?

I just installed AnkhSVN to have subversion support from within Visual Studio 2010. I noticed I had to go to Tools > Options > Source Control to select the current source control plugin.

At the moment, I'm working on multiple projects using different version control systems. For instance, I also have some projects in Mercurial, for which a VS source control plugin is available.

Is there any way to specify the source control plugin on a per-solution basis? Or can VS detect the used vcs automatically? What are the best practices in this respect?

Edit: a google search led me to How to configure Visual Studio to use different source control providers and Can Perforce and SourceSafe co-exist in Visual Studio?. Both cover the same ground, but appear to be specific to specific vcs and lack a satisfying general answer. I'm looking for a general answer here.

like image 904
Marijn Avatar asked Nov 29 '11 08:11

Marijn


People also ask

How do I change the source control code in Visual Studio?

Visual Studio Code and Git Source ControlLaunch VS code, and in the left-hand menu, click on the Source Control icon for Git. It gives two options – Open Folder and Clone Repository. We can open a git repository folder or clone from a GitHub URL. We already set up a GitHub repository in the previous article.

How do I disable source control in Visual Studio?

In the Project Explorer, select the file to remove. If you select a folder, project, or solution, any eligible child items will also be removed. choose Source Control > Remove or press Ctrl+R, R.


1 Answers

There is unfortunately no good answer here. You will simply have to go in and manually change you visual studio source control provider settings before you open the project. This is a limitation of how this particular plugin system works, and will probably take a new version of visual studio to specifically address it.

This is an instance where visual studio works better for the enterprise shop with standardized source control tools, and not as good for a contractor working with multiple clients across an array of technologies.

like image 176
Joel Martinez Avatar answered Oct 09 '22 04:10

Joel Martinez