Marketing-wise, one of the problems Regionerate is facing with is that most developers think Regionerate does #regions, and if you use it, your code will be gianormous, because it will allow you to stuff your face full of code and stick it in a #region.

One of the features that will be released as part of v0.7.5 is the Holy War Prevention Switch (its already available in the trunk & nightly build, in case you want it), which simply allows you to override all #regions in the application and turn them into comments or “invisible” regions.

Besides the Holy War Prevention Switch, I would like to use the new Online Code Layout Editor in order to market Regionerate as a tool that does not force you to use #regions. And yes, it is too late to change the name “Regionerate”

So I was thinking that the new code layout editor will let you create Areas in which you place elements in. These areas may be rendered as plain areas, #regions, or with a comment on top.

So what do you think of this idea? Comments will be appreciated.

From now on, all announcements will be posted in the devblog, so you won’t have to keep your eye for updates from two different feeds.

The new website is a lot more concise and clear, in my opinion. Do you like it?

I think that the first thing you will look in a controller is its actions, so this code layout just puts them first, then organizes the rest.

The actions are ordered by name (which would be the fastest way to locate an action), then by ascending parameter count (Useful since usually you would have a action called Edit without any parameters, that would show the Edit view, and then an Edit action with parameters, which will accept the form data)

To add this code layout to your code layout browser, just download this and decompress it to “%programfiles%\Regionerate\My Code Layouts\Class Styles”.

When you hit Regionerate This, you should see it in the code layout browser:

ASP.NET MVC Controller Code Layout

Try it out, let me know what you think. (I’m just waiting for some input from you guys before adding it into the installation)

Download ASP.NET MVC Controller Code Layout (first draft)

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

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?

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.

These Code Layouts are not designated to be primary Code Layouts, but are very useful when trying to standardize the usage of a framework or a certain coding style.

I’ve been getting great feedback regarding Contract First, NUnit Test Fixture and the POCO layout and want this to be appealing to more people by shipping more specific Code Layouts.

Can you think of frameworks this might be suitable for?

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?