Using Visual Studio 2013 with TFS and Git repositories on same project

August 31, 2014 · 1 min read

With Visual Studio 2013 is a nightmare to keep a git repository but having TFS as a source control plugin activated when we load the solution. Every time we open the solution, by default Visual Studio will select the Git provider and ignore completely TFS (oh, irony…)
To solve that, I had to move out the .git folder to an external folder and point the git dir to the actual source code folder. So an example is: 

C:\Git\ (where I have my different .git repositories per project stored) 

-- C:\Git\ProjectOne\.git 

-- C:\Git\ProjectTwo\.git 

C:\Code (where I have all projects source code) 

-- C:\Code\ProjectOne\.git (this is a file, not a folder anymore) 

-- C:\Code\ProjectTwo\.git (this is a file, not a folder anymore) 

 So, this .git file has to be generated as: 

$ echo "gitdir: /git/ProjectOne/.git" > .git

After doing this, you can open Visual Studio and TFS will be selected by default. You still be able to run a “git status” or any git command as you always did before.

This article is part of the GWB Archives. Original Author: Tiago Salgado

New on Geeks with Blogs

  • We Won The One Award I Actually Care About

    Full Scale made the Inc. 5000 for the fifth year straight, the 12th listing across my three companies. Here is why the one award you cannot buy is worth stopping for.

  • Your Customers Build the Features Now

    I let a tool I liked sit dead for a year rather than build the features I wanted. An MCP server meant I never had to, and your customers can do the same to your product.

  • Get the Size of a Directory in Linux the Easy Way

    du -sh for the quick answer, ncdu for the cleanup, df for the disk itself: every command for checking directory size in Linux, plus why du and df never agree.

  • Vim Search and Replace: The Ultimate Guide

    One :%s command replaces every match in a file before a find dialog would even open. The Vim substitute patterns worth the muscle memory: flags, ranges, capture groups, and multi-file edits.