Has anyone managed this problem? All other Mercurial facilities are working fine inside VS.
+1
A:
Two things to try:
- Make sure you reinstall VisualHG after installing Visual Studio 2010 (this may not be "necessary," but it's often needed for plugins of various sorts anyway).
- Make sure you have VisualHG selected as the active source control plug-in. Go to Tools -> Options -> Source Control -> Plug-in Selection and make sure VisualHG is selected.
James McNellis
2010-05-31 01:00:03