Regionerate archive
An automatic layout enforcement tool for the C# programming language.  
Main
Introduction
Tutorials
Download
Gallery
Blog
Documentation
Discuss
Source



 Subscribe in a reader

 Subscribe by e-mail



Ads Via The Lounge

Omer Rauchwerger
omer at rauchy dot net



New Version Available - v0.6.1.0, published Saturday, June 30, 2007

Two small features are included:

  1. You can now disable member count in region declarations. (thanks for the idea, eborman)
  2. The settings dialog has a new "Edit" button which allows you to edit your custom Code Layout xml files directly from the settings dialog.

Also, two bugs are fixed on this one:

  1. Destructors aren't handled (thanks MisterG)
  2. Code Layout validation fails (thanks ggreig)

You can download this version at the Downloads page.

Labels: , ,


0 comments. Add a comment.


New Version Available - v0.6.0.8, published Thursday, June 28, 2007

Two bugs are fixed on this one:
  1. Code within Comments is copied as normal code. (thank you MisterG!)
  2. When clicking the Refresh button on the Settings form, The IDE throw nasty errors if the loaded Code Layout is invalid. (thanks Rachit)
You can download this version at the Downloads page.

Labels: ,


0 comments. Add a comment.


New Version Available - v0.6.0.7, published Wednesday, June 27, 2007

Two significant bugs are fixed on this one:
  1. Static identifer is recognized only after access modifier (thanks to friedmal for discovering)
  2. Properties not recognized - Properties with a different accessor between the getter and the setter. (thanks to Kevin for discovering)

You can download this version at the Downloads page.

Labels: ,


0 comments. Add a comment.


New Version Available - v0.6.0.6, published Tuesday, June 26, 2007

Two critical bugs are fixed on this one:

  1. "Event attributes orpahned after event added to a region" (thanks to eborman for discovering)
  2. "Multiline attributes" (known issue from v0.6.0.0)

You can download this version at the Downloads page.

Labels: ,


0 comments. Add a comment.


New version available - v0.6.0.5, published Monday, June 25, 2007

This small update includes:

You can download this version at the Downloads page.

Labels: , ,


0 comments. Add a comment.


v0.6 Includes #develop Add-In, published Thursday, June 21, 2007

Freshly compiled, a new add-in for the kick-ass #develop IDE is available from v0.6.

Read more about the differences between the #develop add-in and the Visual Studio add-in at this post in the development blog.

Labels: ,


0 comments. Add a comment.


Getting Started With Code Layouts, published Sunday, June 17, 2007

Here's a quick guide to get you started on writing your own Code Layout.
Code Layouts are simply XML files which follow the Code Layout Schema.

The Code Layout Schema (CodeLayoutSchema.xsd) can be found in your installation directory.
If you are using Visual Studio, the Code Layout Schema is copied during installation into your Visual Studio Schemas directory.

Here are the steps neccesary to start writing a custom Code Layout in Visual Studio:

  1. Create a new XML file in Visual Studio (File->New->File->XML File->Open)
  2. Type in "<CodeLayout xmlns="http://regionerate.net/schemas/0.6/CodeLayout.xsd">" (substitue 0.6 to the current version you are working with).

If you are using Visual Studio, the file should be linked to the Code Layout Schema immediatly, and you should be able to receive intellisense assistance.

If you are not using Visual Studio, or for some reason you are not getting intellisense assitance:

  1. Open the Properties window for the XML file.
  2. Choose "Schemas" and click on the button.
  3. Click on "Add" and browse for the CodeLayoutSchema.xsd file under your installation directory. (typically C:\Program Files\Regionerate)
  4. Click OK. The XML file is now validated by the Code Layout Schema.

The Code Layout Schema structure is pretty simple, I'm sure you'll manage from here.

Once you have your Code Layout all ready, you can easily load it into the Visual Studio add-in by following these steps:

  1. Click on Tools->Regionerate Settings.
  2. Under "Code Layout" check "Use Custom".
  3. Hit the "Browse" button and browse for your custom Code Layout.
  4. Click "Save".
If you are having any difficulties with the structure of the Code Layout Schema, post a comment this post and I'll expand on the topic.

Labels: ,


8 comments. Add a comment.


Your Nighty Regionerate, published Wednesday, June 6, 2007

The development of the Regionerate NAnt Task is complete and will be available from v0.4, read all about it in http://blog.regionerate.net/2007/06/nant-task.html.

0 comments. Add a comment.


Donations, published Sunday, June 3, 2007

Developing Regionerate comes with the costs of web hosting, caffeine and the occasional 3am pizza.
If you enjoy Regionerate and would like to help keep it alive you are welcome to feed me (donate money, that is) by clicking on the PayPal button.







1 comments. Add a comment.


How To Integrate Regionerate With NAnt, published Saturday, June 2, 2007

Regionerate can easily run as part of your NAnt build machine. Warning: boring details ahead.

The installation package comes with an assembly called Regionerate.Presentation.Addins.NAnt.Tasks.dll which contains the Regionerate NAnt Task.

You should provide this task with a few details about what it should do, such as which projects or solutions it should run on and which Code Layout it should apply on them.

Here are the steps which should be performed in order for Regionerate to run under NAnt:

1. Tell NAnt to load the Regionerate NAnt Task assembly by adding the following element to your build file:

<target name="setup">
<loadtasks assembly="C:\Program Files\Regionerate\Regionerate.Presentation.Addins.NAnt.Tasks.dll">
</target>

2. Call the Regionerate NAnt Task called "rgn". For example:

<target name="regionerate" depends="setup">
<rgn noInfo="true" noWarn="false">
<solutions>
<include name="Solution1.sln" />
</solutions>
<ignoredProjects>
<include name="IgnoredProjectFromSolution1.csproj" />
</ignoredProjects>
<ignoredFiles>
<include name="IgnoredFileFromAllProjectsInSolution1.cs" />
</ignoredFiles>
</rgn>
</target>

Here is a detailed explanation of the different elements and attributes you can use in this task:

rgn element - Starts the Regionerate task.
rgn/layout attribute (optional, defaults to the default Code Layout) - Sets the Code Layout that will be used to apply layout within this task.
rgn/noInfo attribute (optional, defaults to false) - Determines whether progress information should be displayed.
rgn/noWarn attribute (optional, defaults to false) - Determines whether non-critical warnings should be displayed. Note that critical warnings will always be shown.
rgn/solutions element (optional) - Regionerates solution (.sln) files.
rgn/solutions/include element (mandatory) - Regionerates a solution file.
rgn/solutions/include/name attribute (mandatory) - The path to the .sln file.
rgn/ignoredProjects element (optional) - Ignore certain project (.csproj) files from all solutions.
rgn/ignoredProjects/include element (mandatory) - Ignore a certain project (.csproj) file.
rgn/ignoredProjects/include/name attribute (mandatory) - Name or partial name of a .csproj file. (e.g: "MyProj.csproj" for all projects which include "MyProj.csproj" in their file name or ".Tests" for all projects that include ".Tests" in their file name)
rgn/projects element (optional) - Regionerates project (.csproj) files.
rgn/projects/include element (mandatory) - Regionerates a project file.
rgn/projects/include/name attribute (mandatory) - The path to the .csproj file.
rgn/ignoredFiles element (optional) - Ignore certain code (.cs) files from all solutions and projects.
rgn/ignoredFiles/include element (mandatory) - Ignore a certain code (.cs) file.
rgn/ignoredFiles/include/name attribute (mandatory) - Name or partial name of a .cs file. (e.g: "WorkItem.cs" for all code files which include "WorkItem.cs" in their file name or "Attribute" for all code files that include "Attribute" in their file name)

3. Optionally, you may wish to check-in any modifications made with a message such as "Nightly Regionerate". Since this task is performed in a different way for every source control provider, it will not be discussed here for now. If you need help with a specific source control provider, comment this post and maybe I'll expand on it.

Labels:


0 comments. Add a comment.


From the Development Blog
 		From My Personal Blog
Read more news from
  • May 2007
  • June 2007
  • July 2007
  • August 2007
  • November 2007
  • December 2007
  • January 2008
  • August 2008

    Contribute
    I'm currently looking for good people to help me with the remaining development tasks for Regionerate v1.0. If you like Regionerate and want to be a part of it, contact me at omer at rauchy dot net.

    Release plan
    • Private Alpha (v0.2) -- complete.
    • Private Beta (v0.4) -- complete.
    • Public Beta (v0.6) -- complete.
    • Beta 2 (v0.7) -- current stage.
    • Release Candidate (v0.8) -- being developed.
    • Release (v1.0)


    		•
    Omer Rauchwerger omer at rauchy dot net
    Feed me
         		Distributed under the
    GNU general public license.