Reputation: 1155
I'm having an issue with VS2013 which I had connected to my visual studio online account, and was using TFS source control just fine up until I installed Git. Now it seems that "Microsoft Git Provider" keeps overriding my settings for source control even after I manually change it back to TFS, or none then TFS. So now I just want to remove it all together. I tried uninstalling everything Git related, but it still remains. I even uninstalled VS2013 completely, then reinstalled, and it's still there.
Upvotes: 9
Views: 6177
Reputation: 6764
Just run the installer again...
In my case, the installer was Microsoft.TeamFoundation.Git.Provider.msi
and choose the remove
option.
Upvotes: 0
Reputation: 10265
Update 2:
Here's an extension that disables MS Git provider on opening a git solution: http://visualstudiogallery.msdn.microsoft.com/146b404a-3c91-46ff-932a-fb0f8b826f94
The solution doesn't seem to work anymore (as also mentioned in the blog post):
For the ones running into this article and wanting to disable the provider for other reasons (performance or files being read-only for refactoring by Resharper), I did run into this registry hack to permanently remove the MS GIT source control provider:
https://blog.rendle.io/disable-the-git-source-control-add-in-in-vs2013-permanently/
tl;dr:
close VS2013 then delete this whole key (or the one with a GitSCCProvider value under it):
HKEY_CURRENT_USER\Software\Microsoft\VisualStudio\12.0_Config\SourceControlProviders\{11b8e6d7-c08b-4385-b321-321078cdd1f8}
Search the registry for the same GUID 11b8e6d7-c08b-4385-b321-321078cdd1f8
and remove those values or entries
too.
Edit:
if you need to use a TFS GIT repository and related information from Team Explorer (like builds, etc), don't delete the GIT SCC provider because that will break too.
Upvotes: 12
Reputation: 3347
Following did the trick for me (source: http://researchaholic.com/2015/02/02/remove-the-microsoft-gitprovider-from-visual-studio-2013/)
Note two extra steps I added:
1. I did make a backup of all registry keys by exporting them before deleting.
2. I also deleted all instances of {11b8e6d7-c08b-4385-b321-321078cdd1f8}
Upvotes: 1
Reputation: 171
I used procmon to see that this dll was being accessed by visual studio when switching to the Microsoft Git Provider.
"C:\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer\Microsoft.TeamFoundation.Git.Provider.dll"
I edited the permissions for the dll so that the user "Everyone" had no permissions for it, and VisualStudio stopped switching back To "Microsoft Git Provider" every time at startup. Doing this means even if you try to select "Microsoft Git Provider" for the current source control plugin it does nothing and instead just shows your previous selection.
Upvotes: 17
Reputation: 1155
Thanks @Ade-Miller, that's actually what I needed to hear.
Turns out my issue was that one of the parent level folders of the project I was working in was set as a repo in Git: C:\users[me]. Not sure how that happened. But apparently VS doesn't like trying to figure out what the hell you've got going on in that sort of scenario, even though the project itself was set to use TFS. Deleting the ".git" folder from the top level folder made everything start to behave better.
Upvotes: 3