**UPDATE: I am using the Castle MonoRail project trunk code, NOT RC2 **
REASONS:
I’ve had a few friends ask me what is MonoRail and how do I set it up? I decided to go from the ground up here. There is nothing here that you can’t get from the Castle website documentation. I just want to grok this stuff and like Mr. Torvalds says, “Talk is cheap, show me the code". I also want to learn how to unit test in this environment. I’ve heard the great things about Ruby on Rails (RoR from now on), but want to make that migration slowly.
Please don’t laugh if this is too beginning for you. I will eventually get to some advanced topics like:
and much more after the scar tissue starts to gather (one mentioned below).Please be patient with me and if you are using MonoRail in production, please make sure I stay on the correct path (JoeyDotNet, Scott Bellware and the Dovetail team, and Billy McCafferty are a few that I know of).
Now we begin.
SETUP:
My current main folder structure in my source control (Subversion) is like so:
I also use Ankh for my Subversion plug-in in Visual Studio 2005 (hence the green checkmarks in the image above and future images.)
I keep all my dependent libraries in the lib folder (yes, Jason, we’re not morons…I know)
Once the default structure is setup, you need to setup your folders so that MonoRail will work properly:
Notice the folder structure:
Project Root +Content -—-css -—-images +Controllers +Models +ViewComponents (future post) +Views -—-components -—-(matching controller named folders containing vm files) -—-layouts (next post) -—-rescues (next post)
This is all provided on the Castle website documentation.
I am currently using shared hosting (WebHost4Life) and it has served it’s purpose. I recently posted about how they added the .rails extension to the server so that I can feel more legitimate about using rails than having to use a different extension, explained here and in my previous post. The installation instructions on the Castle website documentation are very user friendly. I personally took the **sample solution** and started from there. It worked great. Just build it locally and upload your web project to your web host. I personally check into a subversion repository and use CruiseControl.NET for my automated continuous integration and during that process my NAnt script handles deployment.
I’M NOT A DESIGNER:
No matter how hard I try to design sites, I can’t make them appealing to the human eye. I LOVE Open Source Web Designs. It has over 2000 designs and gives me a place to start. The site I’m using, JasonMeridth.com, for this example is create by Node Thirty Three (I firmly believe in giving the designers their dues) and know it will do it’s job.
NOTES TO PAY ATTENTION TO:
If, sorry, when you setup your Test projects make sure to reference the correct assemblies needed for unit testing with MonoRail. They are Castle.MonoRail.Framework, Castle.MonoRail.TestSupport, and my unit testing framework of choice is NUnit, so I reference nunit.Framework. Also don’t forget to reference the project you are unit testing. In this case it is my JasonMeridth project.
I’m still trying out the abstract base test class that the Castle group has created, AbstractMRTestCase.
TIP: Currently I’ve learned that if you do the following (This is only a serious rough draft, please no comments on test names or formatting):
1: using System;
2: using Castle.MonoRail.TestSupport;
3: using JasonMeridth.Controllers;
4: using NUnit.Framework;
5:
6: namespace JasonMeridth.Tests.Controllers
7: {
8: [TestFixture
Comments Link to heading
Joey Beninghove: Good stuff. This should definitely help more folks to start using MonoRail. I’m currently on my 3rd “professional” MonoRail project and I can’t ever imagine having to go back to “classic” Web Forms. Also, regarding unit testing, you’ll definitely want to check out the BaseControllerTest class (assuming you’re working from the trunk, which I do recommend). BaseControllerTest is a much better way to drive out your controllers via TDD and I’ve used it successfully on my last 2 projects. Funny you mention RoR, because I’m actually in the process of learning Ruby (and Rails) on the side and I’ve just been blown away by it. I love the simplicity of MonoRail, but it truly is held down by being tied to the static languages of .NET. From what I’ve seen so far, that beauty in simplicity in RoR is 10-fold of what we can get with MonoRail on .NET. Anyways, btw, thx for the tip/link to Open Source Web Design. Hadn’t seen them before. Looks like a great place for us creatively-challenged folks to get the design ideas bumping around in our heads.
Jason Meridth: Awesome!! Thanks Joey, I will check that BaseControllerTest class. I’m using the trunk. :) I will head down the RoR path soon, but baby steps for me. I look forward to any RoR posts from you in the future (hint, hint) :) OSWD is awesome. Glad I could get that out there.
Sean Chambers: I have to agree with Joey here. I have done about three projects with Windosor/MonoRail as well and I couldn’t imagine going back to WebForms. Someone would have to drag me kicking and screaming =)
Jason Meridth: I’m starting to feel the same way with just the little I’ve done so far. I may be tapping into your knowledge later Sean. Thanks for the info.
Joe: Hey man, looks like a good post. You beat me to the punch, I’ve been working on a Monorail introduction myself. As for unit testing, that is actually no longer the recommended way to test. Check out this page http://using.castleproject.org/display/MR/TDDingControllers that shows the new recommendations for TDD with MR. The old way (inheriting from AbstractMRTestCase) is meant to be used internally. Keep up the great posts! Joe
Jason Meridth: @Joe Thank you for that link. I appreciate the support. Post about MonoRail anyway bro, another perspective is always good.