Using Git with Visual Studio [closed] – Dev

The best answers to the question “Using Git with Visual Studio [closed]” in the category Dev.


As a long-time Visual SourceSafe user (and hater) I was discussing switching to SVN with a colleague; he suggested using Git instead. Since, apparently, it can be used as peer-to-peer without a central server (we are a 3-developer team).

I have not been able to find anything about tools that integrate Git with Visual Studio, though – does such a thing exist?

What are the technologies available for using Git with Visual Studio? And what do I need to know about how they differ before I begin?


I use Git with Visual Studio for my port of Protocol Buffers to C#. I don’t use the GUI – I just keep a command line open as well as Visual Studio.

For the most part it’s fine – the only problem is when you want to rename a file. Both Git and Visual Studio would rather that they were the one to rename it. I think that renaming it in Visual Studio is the way to go though – just be careful what you do at the Git side afterwards. Although this has been a bit of a pain in the past, I’ve heard that it actually should be pretty seamless on the Git side, because it can notice that the contents will be mostly the same. (Not entirely the same, usually – you tend to rename a file when you’re renaming the class, IME.)

But basically – yes, it works fine. I’m a Git newbie, but I can get it to do everything I need it to. Make sure you have a git ignore file for bin and obj, and *.user.


In Jan 2013, Microsoft announced that they are adding full Git support into all their ALM products. They have published a plugin for Visual Studio 2012 that adds Git source control integration.

Alternatively, there is a project called Git Extensions that includes add-ins for Visual Studio 2005, 2008, 2010 and 2012, as well as Windows Explorer integration. It’s regularly updated and having used it on a couple of projects, I’ve found it very useful.

Another option is Git Source Control Provider.


I’ve looked into this a bit at work (both with Subversion and Git). Visual Studio actually has a source control integration API to allow you to integrate third-party source control solutions into Visual Studio. However, most folks don’t bother with it for a couple of reasons.

The first is that the API pretty much assumes you are using a locked-checkout workflow. There are a lot of hooks in it that are either way expensive to implement, or just flat out make no sense when you are using the more modern edit-merge workflow.

The second (which is related) is that when you are using the edit-merge workflow that both Subversion and Git encourage, you don’t really need Visual Studio integration. The main killer thing about SourceSafe’s integration with Visual Studio is that you (and the editor) can tell at a glance which files you own, which must be checked out before you can edit, and which you cannot check out even if you want to. Then it can help you do whatever revision-control voodoo you need to do when you want to edit a file. None of that is even part of a typical Git workflow.

When you are using Git (or SVN typically), your revision-control interactions all take place either before your development session, or after it (once you have everything working and tested). At that point it really isn’t too much of a pain to use a different tool. You aren’t constantly having to switch back and forth.


Git Source Control Provider is new plug-in that integrates Git with Visual Studio.