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 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 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.

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?