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

  • AI for GitHub Collaboration? Maybe Not So Much

    No doubt GitHub Copilot has been a boon for developers, but AI might not be the best tool for collaboration, according to developers weighing in on a recent social media post from the GitHub team.

  • Visual Studio 2022 Getting VS Code 'Command Palette' Equivalent

    As any Visual Studio Code user knows, the editor's command palette is a powerful tool for getting things done quickly, without having to navigate through menus and dialogs. Now, we learn how an equivalent is coming for Microsoft's flagship Visual Studio IDE, invoked by the same familiar Ctrl+Shift+P keyboard shortcut.

  • .NET 9 Preview 3: 'I've Been Waiting 9 Years for This API!'

    Microsoft's third preview of .NET 9 sees a lot of minor tweaks and fixes with no earth-shaking new functionality, but little things can be important to individual developers.

  • Data Anomaly Detection Using a Neural Autoencoder with C#

    Dr. James McCaffrey of Microsoft Research tackles the process of examining a set of source data to find data items that are different in some way from the majority of the source items.

  • What's New for Python, Java in Visual Studio Code

    Microsoft announced March 2024 updates to its Python and Java extensions for Visual Studio Code, the open source-based, cross-platform code editor that has repeatedly been named the No. 1 tool in major development surveys.

Subscribe on YouTube