I really hoped to get Regionerate running quickly on Visual Studio 2010 Beta 2.

Unfortunately, since there are several breaking changes with Visual Studio 2010’s extensibility model, I found myself messing around with it too much.

I’m not giving up, but I just need to clear an afternoon for it. Meanwhile, Since I’ve been getting a whole bunch of requests for quick support for 2010, here’s a quick workaround:

1. Go to “%programfiles%\Regionerate”.
2. Make a copy of “Regionerate.VS2005.AddIn” and call it “Regionerate.VS2010.AddIn“.
3. Open it with notepad, change Extensibility/HostApplication/Version to 10.0 and save the file.
4. Open up regedit.exe.
5. Go to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Visual Studio\10.0\AutomationOptions\LookInFolders.
6. Add a string key named “C:\Program Files\Regionerate\” (or wherever you had Regionerate installed)
7. Start Visual Studio 2010 and go to Tools/Regionerate Settings.
8. Turn off Automatically collapse regions after Regionerating. (Yes, they won’t collapse until I fix it)

Update: Thanks for Mr. Bungle for reminding me to add step 4-6. Mike Patton enthusiasts FTW!

Add your comments here if you have any problems using this workaround.

I was wondering where people use attributes the most, so I will appreciate it if you could answer this short poll.

Over the past 6 months I got a lot of feature requests by e-mail, and I would like to thank everybody for sending great ideas.

Since releasing a version can be a long procedure, I would like to change my release habits with Regionerate and stop releasing versions for bug fixes. Now that the source code is freely available at Assembla, bug fixes can be obtained by getting the source code and compiling.

I will release a new version for new features only, and of course, those releases will include all the bug fixes that were committed until the release date.

v0.7 is coming up with a couple of new features and a couple of bug fixes.

Thank you all for your patience and kind words over the last months.

See, the problem is that if the symbol is empty, any comment block that starts with at least two slashes will be considered as a Regionerated comment region. For example, if the symbol is”*”, Regionerated comment regions would look like:

// * Private Fields (3)

But if the symbol is “” (empty), the same region would look like

// Private Fields (3)

This looks exactly like any other comment, and must be removed before actually Regionerating to prevent junk from piling up. However, I did minimize the bug’s severity by allowing triple-slash comment blocks such as Xml documentation

I was thinking of creating an “IsOperator” filter (similar to the “IsConstructor“) in the PutMethods statement. This will allow you to create regions for your operators.

However, since most people do not overload operators, I decided to hold on this, until I see that it is actually needed.

So if you want to be able to create regions for your overloaded operators, let me know by commenting this post.

1. /* */ comment blocks are not attached to members.
2. Multiple types in Generic members ( e.g. IDictionary&lt int, string &gt) are not handled.

Both issues will be fixed tonight, watch for comments for a new version.

Thanks to Lior and Tomer for finding the bugs.

Don’t even bother Regionerating protected internal members with Regionerate v0.4.0.0. It goes insane. I will have a fix out tonight. Watch for comments on this post.

Thanks to Lior for finding the bug!