Onward and Upward

Blog archive

Visual Studio Git Tools Updated

Microsoft released a new version of Visual Studio Tools for Git yesterday, that adds some welcome functionality.

The update is version 0.8.0.0 (so it's still in the preview stage). The two key additions are a "Resolve Conflicts" page and a new scheduled builds page that allows nightly builds.

Resolving conflicts is a multi-step process that must be completed before pulling or merging project files. First you click on the conflicted file to get information, then compare versions, then sort it all out. When that's done (and all the files are moved to the Resolved category), the pull or merge can proceed.

An "Abort Merge" change is coming, according to the blog entry, but not available yet.

Running the nightly build involves creating a build process (as with resolving conflicts, step-by-step instructions are included). The builds can be triggered in multiple ways: manually, automatically with each code check-in, or on a rolling basis.

Visual Studio Tools for Git is available only with Visual Studio 2012 Update 2 CTP. The CTP, as I wrote earlier this week, is currently on its fourth iteration. That's expected to be the last one before the official release of Update 2. If you're not on Visual Studio 2012, you'll first need to have that; then apply Update 2; then add the Git tools.

Visual Studio Tools for Git is an extension for Team Explorer, and enables the use of Team Foundation Service (TFS)-hosted Git projects. The last Git tooling update was a little less than a month ago. Most Git projects, including Git itself, are hosted on GitHub.

Update: The new release fixes several important bugs, according to this new blog entry by the Visual Studio team. Both bugs have to do with the "open-source libgit2 library for the "core.ignorecase" setting", Microsoft's Andy Lewis writes. The bugs could result in your Git repository being corrupted; in other words, if you're not on the 0.8.0.0 version of Git tools, run, don't walk, to your computer and update them.

Posted by Keith Ward on 03/07/2013


comments powered by Disqus

Featured

  • Using Local AI to Cut Copilot Usage-Based Billing Shock

    After being gobsmacked by the new billing plan using almost all my monthly credits in one or two days, I tried pushing some Copilot-style coding work onto local models in VS Code. What I found was less "free AI" and more "pick your pain": cloud charges on one side, heavy local resource use and long waits on the other.

  • .NET 11 Preview 5 Focuses on Performance, Productivity and Safer Code

    .NET 11 Preview 5 focuses on under-the-hood runtime performance gains, streamlined APIs and language features that reduce boilerplate, plus built‑in security checks and incremental ASP.NET Core and EF Core improvements aimed at everyday developer productivity.

  • VS Code 1.124 Focuses on Agent Autonomy and Parallel Sessions

    Microsoft's June 2026 VS Code update turns on Autopilot by default and adds background sending for agent sessions.

  • Developing Agentic Systems in .NET: From Concept to Code

    ZioNet founder Alon Fliess previews his Visual Studio Live! San Diego session on building true agentic systems in .NET -- covering the cognitive loop, MCP tool integration, multi-agent orchestration and enterprise hosting and governance with the Microsoft Agent Framework.

Subscribe on YouTube