Tags
.NET (42), Meetups (37), dotnetoxford (33), Git (12), Productivity (12), Career (10), LINQPad (8), PublicSpeaking (7), YearInReview (6), Docker (6), CLI (5), Testing (5), Software (4), Workflowy (4), Azure (4), BestPractices (4), Blog (4), Cake (3), Kubernetes (3), Vi (3), Snippets (3), Resharper (2), Podcasts (2), Zoom (2), Xamarin (2), Learning (2), NGINX (2), Evernote (2), Health (2), Debugging (2), DesignPatterns (2), Conference (2), CosmosDB (1), C# (1), Books (1), C# (1), AzureDevOps (1), AzureOxford (1), Aphantasia (1), IoC (1), Hackathon (1), Fonts (1), Documentation (1), dotfiles (1), OGN (1), Microsoft (1), Mocking (1), MVP (1), Neo4j (1), Wyam (1), TimeTracking (1), Powershell (1), RemoteWork (1), Security (1), Serilog (1)Bridging Git and TFS with Git-Tfs
Before reading this, I'd recommend reading my previous post, which goes into the core differences between different Version Control System (VCS) features, with a very strong emphasis on Git.
A love of Git
I started off intending this post to be about the opensource Git-Tfs project. I've used Git at home for both personal and freelance projects for quite a few years, but at work we unfortunately use TFS2008. To allow me to use some of the power of Git at work (at least locally on my computer), I've turned to Git-Tfs.
I quickly realised that in order to explain my reasons for wanting the extra functionality of Git over TFS, I would first have to explain how some core features differ in different Version Control Systems (VCSs). So I decided to split this into two posts - one about Git and VCSs in general, and the other about Git-Tfs. The second post about Git-Tfs can be found here.