Is there anything I have to do to get VisualHG to work with VS2012 RC, or will I just wait for an update?

Thanks

I'm also unable to get VisualHG to work with VS2012 RC. The installation goes through without any errors, but VisualHG does not appear in the list of source control plugins inside VS. Note I do not have VS 2010 installed, only VS2012 RC.

In the meantime I'm using HgSccPackage, but would really like to switch back to VisualHG as soon as it gets support for VS2012.

I had the same issue and got it resolved by repairing the installation of Visual Studio 2012 after installing Visual HG. After that, everything was working fine!

Hope this helps!

I confirm that a Repair solve the issue

Yes repair does solve the issue, but that is really treating the symptom. Surely a better solution would be to fix the actual issue? HgSccPackage install does not suffer this issue so I suspect the problem lies with VisualHG.

I have exactly the same issue. After installing VisualHG there are no error's but it does not show up in Visual Studio 12 RC under tools --> source control. Using the repair option from windows -> add/remove programs of visual studio does fix it. But it took me 3 reboots. (one extra because I still had some windows updates who needed the reboot) Thank god that I have an SSD otherwise it would took me a full workday.

There was no problem with Visual Studio 2012 RC (with July Update). Simply ran VisualHG install and its all ready.

I also had problems getting VisualHg to appear in the Plug-In Selection dropdown in VS2012 RC Professional.

After reading this discussion I did a repair of VS2012 and rebooted but it would still not appear. I rebooted again. Was it there this time? No it was not! To cut a long story short I did the whole thing over several times, sometimes with the repair and sometimes just rebooting, all to no avail. As JPHellemons says "Thank goodness I have an SSD!".

I am a complete newbie to Mercurial, installing VisualHg/TortoiseHg was going to be the first step in trying it out. As a newcomer I had no idea of what was available and seeing mention of HgSccPackage I googled for it, downloaded the most recent version and installed it. Without rebooting I started VS went to Tools|Options|Source Control and there, in the dropdown, was 'Mercurial Source Control Package'. Amazingly enough So was 'VisualHG'.

The solution, therefore, is simple. If you want VisualHG download and install it and if it doesn't appear in the list of Plug-Ins don't bother with all that Repair/Reboot nonsense, simply install HgSccPackage which will cause VS to refresh its Source Control list thereby giving you access to the one that you actually wanted. :-)

henryminute wrote:

The solution, therefore, is simple. If you want VisualHG download and install it and if it doesn't appear in the list of Plug-Ins don't bother with all that Repair/Reboot nonsense, simply install HgSccPackage which will cause VS to refresh its Source Control list thereby giving you access to the one that you actually wanted. :-)

Just wanted to confirm this as working. I installed HgSccPackage and then I was able to select VisualHg.

Super happy for this quick solution as I just did a complete system re-install and ran into enough issues on the way.. last thing I needed was futzing to get VisualHg to work. Now onto something productive :D.

dubbreak wrote:

henryminute wrote:

The solution, therefore, is simple. If you want VisualHG download and install it and if it doesn't appear in the list of Plug-Ins don't bother with all that Repair/Reboot nonsense, simply install HgSccPackage which will cause VS to refresh its Source Control list thereby giving you access to the one that you actually wanted. :-)

Just wanted to confirm this as working. I installed HgSccPackage and then I was able to select VisualHg.

 

Super happy for this quick solution as I just did a complete system re-install and ran into enough issues on the way.. last thing I needed was futzing to get VisualHg to work. Now onto something productive :D.

Same here, thanks henryminute. Much less depressing than having to repair a brand-new install of VS on a clean system.

Thank you henryminute,

This solution also worked for me.

You can also just do a "devenv /setup" from the command line:

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

MikeUpton wrote:

You can also just do a "devenv /setup" from the command line:

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

 

Excellent! Much simpler.

A good tip.

MikeUpton wrote:

You can also just do a "devenv /setup" from the command line:

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

 

I confirm that this solves the problem with VisualHg on VS2012/Windows8. Thank you!

Don't forget: in Windows 8 run the command with admin priviledge. Otherwise, you get an "access is denied" message.

For Visual Studio Express 2012 for Web none of those solutions worked.

The command line used for VS Express was:

"C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\VWDExpress.exe" /setup

...which did not launch VS Express.

I also tried the repair + reboot and installing HgSccPackage, which was also not available for selection in VS after instalation.

Complete instructions for Windows 7 and probably 8

1. Download and install the visualhg msi
2. Start->Visual Studio 12->Visual Studio Tools->right-click Developer Command Prompt for VS2012 + Run as Administrator :

prompt> devenv /setup

Confirming on Windows 8, do this from an admin command prompt and it works.

Windows Key + X -> Command Prompt (Admin)
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\devenv /setup

BeyersCronje wrote:

Yes repair does solve the issue, but that is really treating the symptom. Surely a better solution would be to fix the actual issue? HgSccPackage install does not suffer this issue so I suspect the problem lies with VisualHG.

You should enable VisualHg from within VisualStudio (it's also stated in the main page of VisualHg project here in Codeplex), it's very simple indeed (same procedure as HgSccPackage):

• from VisualStudio, click on Tools -> Options... , then from the left column select "Source Control" and finally (main section "Plug-In Selection") from the main and only combo-box select "VisualHg" as the "current source control plug-in".

This should be the right way and it doesn't require a Reinstall; with previous version of VisualHg the plugin enabled itself automatically, with VS2012 you have to do it manually.

Cheers

edomoli wrote:

BeyersCronje wrote:

Yes repair does solve the issue, but that is really treating the symptom. Surely a better solution would be to fix the actual issue? HgSccPackage install does not suffer this issue so I suspect the problem lies with VisualHG.

You should enable VisualHg from within VisualStudio (it's also stated in the main page of VisualHg project here in Codeplex), it's very simple indeed (same procedure as HgSccPackage):

• from VisualStudio, click on Tools -> Options... , then from the left column select "Source Control" and finally (main section "Plug-In Selection") from the main and only combo-box select "VisualHg" as the "current source control plug-in".

This should be the right way and it doesn't require a Reinstall; with previous version of VisualHg the plugin enabled itself automatically, with VS2012 you have to do it manually.

Cheers

Thanks, but you missing the point of this whole thread. The original problem was that after VisualHG installation, it did NOT appear as one of the options in the combo-box options of plug-in selection.