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

I found out that the Unit Test class style only supports NUnit & MbUnit style fixtures (TestFixture, Test attributes etc.) and does not support the MS-Unit attributes.

Anyway, there is an updated version in the trunk. Should be available on the nightly build.

This means that if you choose to install the nightly build now, the installation will be titled “Regionerate Public Beta 2 (v0.7.3.0)”.

This seems a bit messy, in my opinion, as users might get confused and think that the nightly build is actually v0.7.3.0.

Do you have any suggestions on how to make this process more organized?

It took me about 4 months to commit the patch, sorry guys

You can now choose between tabs or spaces as your indentation character. This should be available in the next release (v0.7.3.0), but is already available in the trunk and nightly build.

Did I mention I really love the fact that now, whenever code is committed, it can be immediately downloaded and installed?

I really want to release v0.7 by AltNetConf Israel, which is happening this Thursday, so no sleep pour moi.

Wish me luck.

Update: [Thursday] Unfortunately, there is no chance I’ll be finishing this today I forgot what it means to release a version. It’ll take me a few more days.

Now you can use multiple tags in the OrderBy statements, for example:

   1:  <PutMethods>

   2:      <OrderBy>

   3:          <Name />

   4:          <ParametersCount />

   5:      </OrderBy>

   6:  </PutMethods>

will place all methods, will order them by name and then will sub-order them by the number of parameters in the method.

Meaning that this piece of code:

   1:      interface IGateway

   2:      {

   3:          void Initialize(Configuration configuration);

   4:          void Finalize(string connectionString, string username, string password);

   5:          void Initialize(string connectionString, string username, string password);

   6:          void Finalize();

   7:          void Initialize();

   8:      }

will turn into:

   1:      interface IGateway

   2:      {

   3:   

   4:          #region Operations (5) 

   5:   

   6:          void Finalize();

   7:   

   8:          void Finalize(string connectionString, string username, string password);

   9:   

  10:          void Initialize();

  11:   

  12:          void Initialize(Configuration configuration);

  13:   

  14:          void Initialize(string connectionString, string username, string password);

  15:   

  16:          #endregion Operations 

  17:   

  18:      }

The good ol’ ForEachClass statement had to be modified a bit (yes, that means you must change your Code Layouts) to allow this.

From now on, use the new ForEach statement and specify the type you want to apply layout to.

For example:

   1:  <ForEach Type="Class">

   2:  ...

   3:  </ForEach>

   4:  <ForEach Type="Struct">

   5:  ...

   6:  </ForEach>

   7:  <ForEach Type="Interface">

   8:  ...

   9:  </ForEach>

This will be available on v0.7, but you can grab the code, compile and use it right now.

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.

The previous survey has helped me to prioritize my tasks so I’ll ask for your help again.
As with the previous survey, I can’t commit to any specific deadlines or promise any feature since this is a spare-time project. It will only help me to prioritize the list.

Some of the features in the previous survey are still not implemented, so these features are on this survey as well.

• Multiple OrderBy commands – Sort by multiple values, e.g: “Sort by name and then by parameters count”. (source)
• Support for nested structs – Put nested structs in regions, just like nested classes. (source)
• Regionerate existing regions’ member – Recursively scan existing regions’ members and Regionerate their internals. (source)
• Monitor file save operation and automatically Regionerate before saving – Prevent the need to hit Ctrl+R every time you add a member and Regionerate the code automatically upon saving. (source)
• Filter by Comment – The ability to create a region for all detached comment sections. (source)
• Couple fields with exposing properties - A popular feature which was originally planned for v2.0. It allows you to create regions that will contain field + exposing property pairs. (source & another thought)
• Span a single OrderBy command over multiple Put statements - Reuse a single OrderBy command (For example, order by name) over multiple Put statements (such as PutProperties, PutMethods, PutDelegates etc.) (source)
• Better control over spacing – Allow complete control over how many spaces are added before, inside and after every region. (source)
• Select which projects & files to ignore when running on solutions and projects inside the IDE - The rgn.exe console application and NAnt task allow you to select which projects & files are ignored by Regionerate. Allow this when clicking “Regionerate This” on projects & solutions inside the Solution Explorer in Visual Studio or Projects Pad in SharpDevelop (source)
• Prompt before Regionerating entire solutions or projects inside the IDE – To avoid a major accidental change, prompt “Are you sure?” before Regionerating entire solutions or projects. (source)
• Allow ”Regionerate This” on solutions and projects to run in the IDE and not directly on files – Allow the user to select whether files are directly accessed by Regionerate (which disables the ability to undo, but faster) or that Visual Studio documents are accessed by Regionerate (which enables undo, but slows things up since it opens all files inside the IDE) (source)
• Filter by matching a method’s parameters – Allow to filter methods by matching a regular expression against their parameter list. This, among other things, will allow you to create better filters for event handlers. (source)
• Auto refresh the Code Layout after changes are made – Monitor activities in the Code Layout file and refresh the Code Layout automatically instead of having to go to the settings dialog and do it manually. (source)
• Regionerate subclasses, structs, an interfaces – (source 1, source 2)

Please let me know if I missed any requests.

Side note: I was thinking of setting the vote count on items from the previous survey to the result they had in order to give them a head start on newer features, but then I thought maybe users might have a different perspective on Regionerate so they should start at zero to avoid giving them an advantage, what do you think?