.NET Musings

I am big fan of distributed version control systems. I happen to prefer Mercurial (and no, I am not interested in engaging in the Hg vs. GIT debate here on the blog.  If you want to have a discussion over a beer, please come find me at one of the many events where I speak and I’d be happy to join you).

I’ve recently went “all in” with Windows 8 and Visual Studio 2012, and I’m very happy, even with the “shouting” menus :-)  However, I didn’t immediately install VisualHG as I wasn’t sure it support VS2012 yet (instead, opting to use the TortoiseHG workbench and the command line options).

Turns out the support is there, there is just a slight glitch in the install.  I don’t know if the glitch is with Visual Studio or VisualHG, but regardless, when you first install VisualHG (make sure you install TortoiseHG first), it is not listed as an option in the Plug-In Selection in Visual Studio Options.

The answer is simple (now that I have found it). Start Visual Studio with the /setup option.  To do this, fire up a command window (make sure you are running as administrator) and enter the following command (the quotes are necessary):

“C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv” /setup

This “wakes up” Visual Studio, and registers VisualHG as an allowable Source Code Control plugin, as in Figure 1.

Figure 1

Once you change the plugin, you will get integration with Mercurial right in Visual Studio.

Figure 2

Happy Coding!

Follow @skimedic Tweet