When happy (sensible intermediate point to commit code, switch to Git, stage changes and review diffs. My usage pattern is something like the following. Mine generally contain (amongst other stuff) the following: *.vcproj.*.userīut this is heavily C++ biased with little or no use of any class wizard style functionality. gitignore file full of the things that shouldn't be in a shared repository. Of course there are instances when it can be nice to click on a button to do some history examination, but I don't miss that very much. I find that Git, working on whole trees as it does, benefits less from IDE integration than source control tools that are either file based or follow a checkout-edit-commit pattern.

You aren't constantly having to switch back and forth. At that point it really isn't too much of a pain to use a different tool.

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). None of that is even part of a typical Git workflow. Then it can help you do whatever revision-control voodoo you need to do when you want to edit a file. 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. 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. 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 first is that the API pretty much assumes you are using a locked-checkout workflow. However, most folks don't bother with it for a couple of reasons. Visual Studio actually has a source control integration API to allow you to integrate third-party source control solutions into Visual Studio. I've looked into this a bit at work (both with Subversion and Git).

Visual studio git integration