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.

So I got some suggestions to use jQuery in order to make the editor hip. I started looking into jQuery UI, and it is awesome.

Also, I’m getting into Ruby on Rails for the back-end implementation, and it is also quite refreshing. The kind people from JetBrains have given Regionerate a license for RubyMine. If you are into Ruby on Rails, you should really check it out.

Off to code.

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?

Its been a strange journey. I’m guessing it was a bit different from an ordinary Joe’s degree, as I came in with about 8 years of professional experience in software development. But when you know a topic and restudy it from the basics, you can reflect on different aspects of it, and still learn a lot.

My Graduate Project

As part of my study program, I must participate in a final project in system analysis, in which I must analyze a client’s domain, propose a software-based solution and develop it.

I am also taking a course on project management by Alex Coman, which also happens to be my graduate project director. Earlier this year, I gave a lecture on Regionerate and its project management. Mr. Coman seemed to like it, so he suggested I base my graduate project on Regionerate.

Not an Ordinary Project

As I said, the graduate project should be based on an actual business (as in “the laundry place down the street”), and we are supposed to analyse its core problems. After doing that, we need to build up a classic 3-tier architecture app and deploy it at the customer’s site.

Needless to say, Regionerate is not a business, its an open-source project, there is no single client to answer all the questions, and it is not a classic 3-tier application.

Mr. Coman is aware of those differences, and he is OK with us going a different path which is more suitable for this kind of project.

So What Are We Developing?

A UI for building code layouts.

According to feedback I got over the years, most of our users use the default code layouts that ship with the installation, and only make tiny differences to it.

Why? Because we are all lazy, and the code layout schema is scary. Heck, I even get scared of it sometimes.

I think that you will agree that one of Regionerate’s strengths is that it is very customizable, but what good is that strength if most users are intimidated by the code layout schema?

So we are going to develop a drag-n-drop interface for creating code layouts, one that will hopefully help more people take advantage of Regionerate’s highly customizable layout abilities.

Your Help

This project will take a few months, and we want to make decisions with you guys. So we will be putting polls on big decisions we need to make.

These polls and the results are part of the graduate project, and Mr. Coman will be inspecting those, so if you want to help us out – participate in the polls and add your comments. These will eventually be pasted into the project paper, so your participation will be appreciated.

Off we go. Wish us luck.

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)

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