Comments on: HOWTO: Get Regionerate to Run on Visual Studio 2010 Beta 2

By: Ben

Ben — Tue, 12 Jan 2010 00:25:05 +0000

Thanks for this, after following the instructions I am back up and running.

Its worth noting though, that to trigger regionerate you cannot use the pop-up right-click context menu. This doesn’t seem to work for me. However I can still configure and use a short-cut key (Ctrl+R by default) and this formats to the default style.

Cheers
Ben

By: Pondy

Pondy — Tue, 15 Dec 2009 06:28:25 +0000

Answer to my own problem:

De-select the option “Automatically collapse regions after Regionerate”.

By: Pondy

Pondy — Tue, 15 Dec 2009 06:19:40 +0000

It might be worth noting that for those of you who have 64bit platforms, you probably won’t find the registry key mentioned because when you run regedit, it will give you the registry for your 64bit applications. Visual studio is still a 32bit application, so you’ll need the 32bit registry editor.

To start 32bit regedit:
%systemroot%\syswow64\regedit

The default install location (ie, the key you will need to create) is:
%ProgramFiles(x86)%\Regionerate

After doing this, you will get a regionerate error message box when you first start up about deprecated methods. There isn’t much you can do here as there is just an ok button.

Unfortunately, this message may have been more significant than I first though because after regionerating my first file, Visual Studio spiraled into unresponsive death.

If anyone finds a way to get it to work on 64bit platforms, send an update.

By: Mr. Bungle

Mr. Bungle — Sun, 29 Nov 2009 23:18:02 +0000

Adding that registry key does mean I have a Tools->Regionerate menu in VS 2010, however I get two exception errors on startup of VS relating to Regionerate. One is a DeprecatedException and the other is an ArgumentException (A command with that name already exists). I can email u screenshots of the exceptions if you want. Going into the Settings dialog for Regionerate works ok, but trying to regionerate a source file using Ctrl+R ends up putting VS into an endless loop, requiring it to be killed. I will stick with using the command line for now, passing the .sln file (so glad you have ability to do this outside the IDE ).

By: rauchy

rauchy — Wed, 25 Nov 2009 05:19:13 +0000

IIdiot. Updated the post. Hope it would work now.

By: Mr. Bungle

Mr. Bungle — Tue, 24 Nov 2009 22:02:06 +0000

Thanks for this info, seems I am missing something tho – I don’t see a Tools->Regionerate Settings menu after launching VS2010. Do I need to copy or register the .addin file somewhere?