PLEAS FOR HELP!

• Can anyone tell me why the docking pane does not stay docked for some users when they restart Visual Studio?
• This plugin is currently broken with VB.NET source files - it interfers with the cursor position. Please feel free to grab the source and figure out why, and let us all know. Even if you let me know how to detect a VB.NET file and disable Ora temporarily, that would be something.

Ora is a Visual Studio 2008 add-in that provides an instant grouped overview of the class, interface or struct you are viewing or editing. Because the members are grouped in the order of your choosing, and the view instantly appears when you click in the code of a class, there is no need to abuse the #region feature. Just keep Ora docked next to the source editor and the equivalent groupings just appear automatically.

New in Build 13

• "Timeout" feature to avoid wasting time due to very large classes

General Information

Note: this plugin is currently only suitable for C# users (it causes weird code editor behaviour in VB.NET, and seems unreliable in C++).

• Regions - When Not to Use Them
• Ora for the Casual User
• Extending Ora with Custom Groupings
• Parts You Might Want To Salvage

Forget using cumbersome #region statements to group together class members. What if you want to see them grouped a different way? And isn't it a bad idea to repeat the same information twice in source code? What if the region structure doesn't reflect the truth? Regions, like comments, should be used to supply information that can't be recovered automatically by an add-in, such as Ora.

Ora is latin for region, amongst other things.

Keywords: visual studio 2008 add-in plug-in grouping regions class overview precis analysis