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.

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

• Comments in member declaration are not supported. For example:

public void Foo() // comment

{
}

– or –

public /* comment */ string Foo

{

get

{

return “foo”;
}
}

• (Updated: Fixed) No support for #ifdef blocks.
• (Update: Fixed) Attributes with line breaks inside are split. for example

[ Attribute( "I", "Cause",

"Problems" ) ]

public void Foo() { }

• (Update: Fixed) Strings containing single “{” or “}” characters drive the construction mechanism nuts. for example:

public void Foo() { string whoops = “}”; }

• Comment sections that start with “(” cause inconsistent behaviour. for example:

///

• Multiple fields declared in a single line are not recognized as fields (meaning, they are left out of Field regions), For example:

public string a,b;

Note: Multiple fields declared in single line is not recommended. Read section 5.1 from this style guide.

• (Update: Fixed) Code inside comments is interpreted as actual code.
• When the “Auto-Collapse” feature is turned off in the Visual Studio add-in, The cursor does not follow selection after Regionerating.

• Strings containing single “{” or “}” characters drive the construction mechanism nuts. for example:

public void Foo() { string whoops = “}”; }

• Comment sections that start with “(” cause inconsistent behaviour. for example:

/// &ltsummary&gt
/// ( Whoops.
/// &lt/summary&gt

• Code inside comments is interperted as actual code.
• When the “Auto-Collapse” feature is turned off in the Visual Studio add-in, The cursor does not follow selection after Regionerating.