Elegant Code » Blogging http://elegantcode.com Tue, 15 May 2012 10:00:00 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 I guess an introduction is in order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/?utm_source=rss&utm_medium=rss&utm_campaign=i-guess-an-introduction-is-in-order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/#comments Sun, 15 Aug 2010 21:50:26 +0000 Andreas Håkansson http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/ Twitter or from my self-titled blog that I have been blogging on up until this point (and might continue doing, haven’t really made up my mind yet what I am going to do with it). However, my real name is Andreas Håkansson and I guess I could describe myself as a nearly 30 year old .NET developer from Sweden, with a passion for pretty much everything in the software engineering / craftsmanship department (hey, why limit yourself to one kind of cake when there’s so much to be had out there!). I am a strong advocator of Open-Source Software and I head the MEF Contrib project, a set of community contributed extensions, tools and samples for the Managed Extensibility Framework, and I have also created the Common Service Factory, a WCF extension that enabled dependency injection in services (it’s a bit dated, but it works like a charm – probably should give it some love as soon as I can find a slice of spare time in my life). Oh yeah, there’s more to me than being a code ninjah – somehow I’ve also managed to get married to my high school sweetheart (12 years since we hooked up and still going strong) and together we have two wonderful boys (3 and 1½ years old – boy do they know how to keep us busy hehe) Well I guess that’s it… now you know a bit about me, and I hope to get to know a bit more about you, the readers of Elegant Code, so please stop by my posts and drop me a line or two. See you there!]]> http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/feed/ 2 What Does Elegant Code Mean to Me? http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/?utm_source=rss&utm_medium=rss&utm_campaign=what-does-elegant-code-mean-to-me http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/#comments Fri, 09 Apr 2010 19:46:38 +0000 John Sonmez http://elegantcode.com/?p=3434 What is elegance? Simply stated. Something that is simple yet effective, delivered with grace. Being simple is not enough. Simple lacking effectiveness is just a waste of time. Simple - Not Effective Simple, but not effective is a foam hammer. You don't want your code to be like a foam hammer. If it can't do what it supposed to do the simplicity just looks like stupidity instead. Effective, but not simple is something that gets thrown away or lamented. It's a Rube Goldberg machine. Rube Goldberg Machine You don't want your code to be like a Rube Goldberg machine either.  Where people look at your code because it is such a spectacle.  You don't want someone to look at your code and immediately think they want to kill you.  Code that evokes murderous rage, tends to get blamed for anything that goes wrong in the system, even if it works perfectly. If you can build something simple and its effective, it still has to be delivered in a graceful way. Consider, the elephant harness... Simple and Effective - Not Graceful Simple?  Yes, it's a box strapped on top of an Elephant, can't get much more simple than that.  Effective?  Yes, looks to me like that elephant will get you where you need to go in that terrain.  Delivered with grace?  Hmm...  Do you want to ride around on an elephant? Even if you nail the first two, with your code, you should make sure it looks and reads good.  No one wants to ride an elephant.  I have seen more than one simple effective design get thrown away because the variables were named things like "cntr" and "banana".

Elegant Code is James Bond

Women love him, men want to be like him and he kills people with a simple sophistication. When people read your code they should think James Bond, not Booger from Revenge of the Nerds. James-Bond Vs. booger
Elegant code to me is code that reads well, does what is is supposed to do and is easy to maintain. Now that I have told you what I think elegant code is, in future posts I will talk more about how to actually write elegant code.

Side Note - Joining Elegant Code

First of all I wanted to publicly thank the other Elegant Coders for inviting me to join their community. I feel honored and esteemed to be joining such a great group of software craftsmen. I also wanted to clear up confusion for anyone who has been following my blog at http://simpleprogrammer.com.  I will still be blogging there, so don't change your RSS feeds, but in addition I will be blogging here at ElegantCode.com.  If you've come here form a link on my personal blog, I encourage you to check out the other excellent bloggers on this site and consider adding Elegant Code to your RSS feed reader.   My personal blog will contain a wider array of topics, but my content here at ElegantCode.com will be centered around the theme of writing elegant code. As always, feel free to email me at john *dot* sonmez *at* gmail.com or follow me on twitter.]]> http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/feed/ 1 Welcome Two New Elegant Coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/?utm_source=rss&utm_medium=rss&utm_campaign=welcome-two-new-elegant-coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/#comments Thu, 15 Oct 2009 19:58:17 +0000 David Starr http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/ I am happy to introduce 2 new Elegant Coders! We are excited to have their contributions to the site and look forward to their wisdom.

Kirstin Juhl

@kirstinj

We are excited to have Kirstin drop wisdom like she has been doing on her current blog: I [heart] Code. From her own bio:

I am a former engineer who writes code. I did Toyota Operating System, Kanban, and Lean in my factories a decade ago, and am fascinated by its use in software development today. You can take the girl out of the factory, but you cannot take the engineer out of the girl, and so I approach everything in life as a problem to solved or optimized. Including software development. I strive to be a craftsman.

I am a mom, and I take lessons from parenthood into my work everyday.

Jason Jarrett

@staxmanade

Jason is a big-time Silverlight maven and the developer behind StatLight, a set of unit testing tools for Silverlight. I knew he was perfect for the tribe when he said, “… and so I added automocking to Unity for Silverlight.”

Yeah. :)

Welcome all.

]]> http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/feed/ 0 FubuMVC From Scratch – Part 4 Persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/?utm_source=rss&utm_medium=rss&utm_campaign=fubumvc-from-scratch-part-4-persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/#comments Wed, 25 Mar 2009 21:22:00 +0000 Ryan Kelley http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/ Previous posts in series:

Persistence is a requirement in virtually every application that we write today, and now the time has come for us to add a persistence model to our FubuMVC app. I know I mentioned moving my samples to the FubuCart source, but I am going to go ahead and implement the persistence piece in the same project the previous articles using, FubuSample. I have also added all the code for this series to the FubuMVC-Contrib project

We will be implementing our persistence model to use NHibernate, Fluent NHibernate, Repository Pattern and UnitOfWork pattern all on top of SQL Express or standard. This will also work for sqllite and other database servers.

Class and Interfaces we have to implement:

  • ISessionSourceConfiguration
  • SQLServerSessionSourceConfiguration
  • IUnitOfWork
  • INHibernateUnitOfWork
  • NHibernateUnitOfWork
  • IRepository
  • NHibernateRepository
  • DomainEntity
  • IDomainQuery
  • FubuSamplePersistenceModel

Note: I put the first two in the list in my Core.Config namespace, and the rest in Core.Persistence

Before we start you probably want to go ahead and add the following references to your core project and Web project

FubuMVC-Persist-Ref

Let’s just work our way down the list and get these files implemented.

ISessionSourceConfiguration

public interface ISessionSourceConfiguration
{
    bool IsNewDatabase { get; }
    ISessionSource CreateSessionSource(PersistenceModel model);
}

SQLServerSessionSourceConfiguration

public class SQLServerSessionSourceConfiguration : ISessionSourceConfiguration
{
    #region Implementation of ISessionSourceConfiguration
 
    public bool IsNewDatabase
    {
        get { return false; }
    }
 
    public ISessionSource CreateSessionSource(PersistenceModel model)
    {
        var properties = GetProperties();
        var source = new SessionSource(properties, model);
 
        create_schema_if_it_does_not_already_exist(source);
 
        return source;
    }
 
    private void create_schema_if_it_does_not_already_exist(ISessionSource source)
    {
        if (IsNewDatabase) source.BuildSchema();
    }
 
    protected IDictionary<string, string> GetProperties()
    {
        MsSqlConfiguration config = MsSqlConfiguration.MsSql2005;
        config.ConnectionString.FromConnectionStringWithKey(“MYDBKEY”);
        config.ShowSql();
        config.UseOuterJoin();
 
        return config.ToProperties();
    }
    #endregion
}

A quick note here: We told SQLServerSessionSourceConfiguration to use a connection string from the app settings file (Web.Config) with a key of “MYDBKEY” This will be important later.

IUnitOfWork

public interface IUnitOfWork : IDisposable
{
    void Initialize();
    void Commit();
    void Rollback();
}

INHibernateUnitOfWork

public interface INHibernateUnitOfWork : IUnitOfWork
{
    ISession CurrentSession { get; }
}

NHibernateUnitOfWork

public class NHibernateUnitOfWork : INHibernateUnitOfWork
{
    private ITransaction _transaction;
    private bool _isDisposed;
    private readonly ISessionSource _source;
    private bool _isInitialized;
 
    public NHibernateUnitOfWork(ISessionSource source)
    {
        _source = source;
    }
 
    public void Initialize()
    {
        should_not_currently_be_disposed();
 
        CurrentSession = _source.CreateSession();
        begin_new_transaction();
 
        _isInitialized = true;
    }
 
    public ISession CurrentSession { get; private set; }
 
    public void Commit()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Commit();
 
        begin_new_transaction();
    }
 
    private void begin_new_transaction()
    {
        if (_transaction != null)
        {
            _transaction.Dispose();
        }
 
        _transaction = CurrentSession.BeginTransaction();
    }
 
    public void Rollback()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Rollback();
 
        begin_new_transaction();
    }
 
    private void should_not_currently_be_disposed()
    {
        if (_isDisposed) throw new ObjectDisposedException(GetType().Name);
    }
 
    private void should_be_initialized_first()
    {
        if (!_isInitialized) throw new InvalidOperationException("Must initialize (call Initialize()) on NHibernateUnitOfWork before commiting or rolling back");
    }
 
    public void Dispose()
    {
        if (_isDisposed || !_isInitialized) return;
 
        _transaction.Dispose();
        CurrentSession.Dispose();
 
        _isDisposed = true;
    }
}

IRepository

public interface IRepository
{
    void Save<ENTITY>(ENTITY entity)
        where ENTITY : DomainEntity;
 
    ENTITY Load<ENTITY>(Guid id)
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>()
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery)
        where ENTITY : DomainEntity;
 
    void Delete<ENTITY>(ENTITY entity);
 
    void DeleteAll<ENTITY>();
}

NHibernateRepository

public class NHibernateRepository : IRepository
{
    private readonly INHibernateUnitOfWork _unitOfWork;
 
    public NHibernateRepository(INHibernateUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public void Save<ENTITY>(ENTITY entity) where ENTITY : DomainEntity
    {
        _unitOfWork.CurrentSession.SaveOrUpdate(entity);
    }
 
    public ENTITY Load<ENTITY>(Guid id) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Load<ENTITY>(id);
    }
 
    public IQueryable<ENTITY> Query<ENTITY>() where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>();
    }
 
    public IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>().Where(whereQuery.Expression);
    }
 
    public void Delete<ENTITY>(ENTITY entity)
    {
        _unitOfWork.CurrentSession.Delete(entity);   
    }
 
    public void DeleteAll<ENTITY>()
    {
        var query = String.Format("from {0}", typeof(ENTITY).Name);
        _unitOfWork.CurrentSession.Delete(query);   
    }
}

DomainEntity

Note: I put both of these classes in my Core.Domain namespace, also XML comments are in Source Repository

public class DomainEntity : IEquatable<DomainEntity>
{
    public virtual Guid ID { get; set; }
 
    public virtual bool Equals(DomainEntity other)
    {
        if (ReferenceEquals(null, other)) return false;
        if (ReferenceEquals(this, other)) return true;
        return other.ID.Equals(ID);
    }
 
    public override bool Equals(object obj)
    {
        if (ReferenceEquals(null, obj)) return false;
        if (ReferenceEquals(this, obj)) return true;
        if (obj.GetType() != GetType()) return false;
        return Equals((DomainEntity)obj);
    }
 
    public override int GetHashCode()
    {
        return ID.GetHashCode();
    }
 
    public static bool operator ==(DomainEntity left, DomainEntity right)
    {
        return Equals(left, right);
    }
 
    public static bool operator !=(DomainEntity left, DomainEntity right)
    {
        return !Equals(left, right);
    }
}

IDomainQuery

public interface IDomainQuery<ENTITY>
    where ENTITY : DomainEntity
{
    Expression<Func<ENTITY, bool>> Expression { get; }
}

FubuSamplePersistenceModel

namespace FubuSample.Core.Domain.Persistence
{
    public class FubuSamplePersistenceModel : PersistenceModel
    {
        public FubuSamplePersistenceModel()
        {
            addMappingsFromThisAssembly();
        }
    }
}

Now that we have all the puzzle pieces in place we need to hook them up and make them do some work. Open up FubuSampleWebRegistry

And add the following code:

protected override void configure()
{
    ForRequestedType<ISessionSourceConfiguration>().AsSingletons()
        .TheDefault.Is.OfConcreteType<SQLServerSessionSourceConfiguration>();
 
 
    ForRequestedType<ISessionSource>().AsSingletons()
        .TheDefault.Is.ConstructedBy(ctx =>
                                     ctx.GetInstance<ISessionSourceConfiguration>()
                                         .CreateSessionSource(new FubuSamplePersistenceModel()));
 
    ForRequestedType<IUnitOfWork>().TheDefault.Is.ConstructedBy(ctx => ctx.GetInstance<INHibernateUnitOfWork>());
 
    ForRequestedType<INHibernateUnitOfWork>().CacheBy(InstanceScope.Hybrid)
        .TheDefault.Is.OfConcreteType<NHibernateUnitOfWork>();
 
    ForRequestedType<IRepository>().TheDefault.Is.OfConcreteType<NHibernateRepository>();
}

With a little luck and all of our mad skills, we should be able to talk to the database now. So we need to plumb our simple product object up to talk to NHibernate. We will do this with a mapping file, and since we are using FluentNHibernate we can do this strongly typed.

Make the following modifications to Product: Extend DomainEntity and get rid of Id Property, it is inherited

public class Product : DomainEntity
{
    public virtual string Name { get; set; }
    public virtual string Description { get; set; }
}

Add mapping file for Product:

namespace FubuSample.Core.Domain.Mapping
{
    public class ProductMap : ClassMap<Product>
    {
        public ProductMap()
        {
            Id(e => e.ID).GeneratedBy.GuidComb();
 
            Map(p => p.Name);
            Map(p => p.Description);
            
        }
    }
}

You may also want to setup your connection string at this point in the Web.Config file, mine looks like this:

<add name="MYDBKEY" connectionString="Data Source=LOCALHOST;initial catalog=FubuSample;Integrated Security=SSPI;" providerName="System.Data.SqlClient" />

I also created an empty database in my local SQL Server instance called “FubuSample” And then I went back to SQLServerSessionSourceConfiguration and changed the value of IsNewDatabase to return true. This will create the schema for the database when the application first runs. There is a multitude of different ways that we can handle this, but this was easy for the tutorial purposes.

Next we will add a behavior to our core project and tell FubuMVC to apply that behavior to all or our ControllerActions.

Create a class named “access_the_database_through_a_unit_of_work” in your Core.Web.Behaviors namespace. The contents will look like this:

public class access_the_database_through_a_unit_of_work : IControllerActionBehavior
{
    private readonly IUnitOfWork _unitOfWork;
 
    public access_the_database_through_a_unit_of_work(IUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public IControllerActionBehavior InsideBehavior { get; set; }
    public IInvocationResult Result { get; set; }
 
    public OUTPUT Invoke<INPUT, OUTPUT>(INPUT input, Func<INPUT, OUTPUT> func)
        where INPUT : class
        where OUTPUT : class
    {
        _unitOfWork.Initialize();
 
        try
        {
            var output = InsideBehavior.Invoke(input, func);
            Result = InsideBehavior.Result;
 
            _unitOfWork.Commit();
 
            return output;
        }
        catch
        {
            _unitOfWork.Rollback();
            throw;
        }
        finally
        {
            _unitOfWork.Dispose();
        }
    }
}

Now to tell FubuMVC what to do, open up Global.asax.cs or your Bootstrapper, wherever you are doing the configuration of FubuMVC. In this project we are doing it in Global.asax.cs Add a new behavior to the section that starts with “x.ByDefault.EveryControllerAction” so it looks like this:

x.ByDefault.EveryControllerAction(d =>
   {
       d.Will<execute_the_result>();
       d.Will<access_the_database_through_a_unit_of_work>();
   });

The last thing we will do is open up HomeController and add this code above the Index action:

private IRepository _repository;
 
public HomeController(IRepository repository)
{
    _repository = repository;
}

I also modified the Index action to go ahead and create some database values before we query for them just so we can test this thing. (I only did this for the tutorial, I swear) So modify the Index action to look like this:

public IndexViewModel Index(IndexSetupViewModel inModel)
{
    var prod1 = new Product {Name = "TestProduct1", Description = "This is a test product"};
 
    _repository.Save(prod1);
 
    var prod2 = new Product {Name = "TestProduct2", Description = "This is a test product"};
 
    _repository.Save(prod2);
 
    var outModel = new IndexViewModel();
 
    var productList = _repository.Query<Product>();
 
    outModel.Products = productList.ToList().Select(x => new ProductDisplay(x));
 
    return outModel;
}

Now with you should be able to run your web app and browse to /home and all this will be executed and you will be on your way to creating a whole bunch of persist able objects for use with your FubuMVC app.

As always, feedback is welcome.

]]> http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/feed/ 9 It’s Official – New Gig started last week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/?utm_source=rss&utm_medium=rss&utm_campaign=its-official-new-gig-started-last-week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/#comments Tue, 24 Feb 2009 19:03:21 +0000 Ryan Kelley http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/ CoachesAid.com. CoachesAid is a High School sports website that is expanding rapidly and it is my task to make this expansion happen as smoothly and as quickly as possible. The past month has been very hectic as I was wrapping up loose ends at my previous engagement. I started my new gig last week, but I have pretty much been building furniture and getting computer and server ready to go. The next few weeks will also be challenging as I start to assemble the team of people that is going to make this all happen. How does this tie into the practice of Elegant Coding? Funny you should ask that, the current infrastructure they are built on is a maintenance nightmare so project number one is to completely redo their entire site infrastructure in ASP.Net, and yes it will be MVC based, but not ASP.Net MVC. I am going to architect and build their new infrastructure from the ground up on FubuMVC. So expect a lot more posts from me on FubuMVC and I may even have questions for you dear reader. Side Note: I just finished deploying to production a small scale site built on FubuMVC, and it ROCKS! There is going to be some stuff that needs to be tweaked out and added to the core, but overall, fully functional MVC framework. I hope I haven’t bored you with too much personal information, but I have to go. (I have several FubuMVC posts stacked up in my queue) -Ryan]]> http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/feed/ 8 Quick 2008 Recap and a few New Years Resolutions http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/?utm_source=rss&utm_medium=rss&utm_campaign=quick-2008-recap-and-a-few-new-years-resolutions http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/#comments Thu, 01 Jan 2009 15:57:06 +0000 Ryan Kelley http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/ Whew, I cannot believe that 2008 is over already, it seems like it just started. 2008 was a great year for me as a developer for several reasons.

Met new People

I was able to meet a ton of new people in 2008, both online through blogs and other communities, and at KaizenConf in Austin. This is probably the single most important thing that happened to me in 2008 because it helped put me into circle of people that share the same thoughts and values about software development that I do.

Alt.Net Introduction

I was also introduced to the Alt.Net movement during 2008. I have been developing software for several years and some of the things I had been doing just didn’t seem quite right, they worked, but they had a smell to them. Enter Alt.Net, this stuff just makes sense. It is smart software development, that revolves around creating highly testable, highly maintainable code that follows the SOLID design principles. I have come to realize that if you just ask yourself “How does this proposed solution adhere to the SOLID principles” you will write much more elegant code.

KaizenConf Open Spaces Conference

This was my first open spaces conference and I didn’t know what to expect but I came away with the feeling that this was the best conference I had ever been to. KaizenConf helped fuel my fire for continuing with more Alt.Net stuff, working on Lean Software Development and KanBan methods, and staying involved with the community. It even spurred me to start blogging more frequently about these topics.

Some 2009 Resolutions

I have a few resolutions I am going to make for the new year, some are computer related, some are not.

  • Blog More – I am targeting 52 blog posts in 2009, that is a little more than double from 2008 and is only 1 per week.
  • Fish more, I love fly fishing, just need to make more time
    • Fly Fish for Bass – talk about fun!
  • Write Elegant Code – I am staying committed to SOLID principles, testability and maintainable code.
  • Learn more about Asp.Net – Especially MVC stuff, I have been doing WinForms development for the past 4 years, so I am looking forward to this one.
  • Learn a new Programming Language – Everybody should do this every year.

I am going to stop there, I don’t want to set any unrealistic expectations for myself during the year. I think all of these are very attainable and I hope that my list has spurred some inner resolution making within you to go out and commit to something new in 2009.

]]> http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/feed/ 2 Hello Elegant Code Readers http://elegantcode.com/2008/12/02/hello-elegant-code-readers/?utm_source=rss&utm_medium=rss&utm_campaign=hello-elegant-code-readers http://elegantcode.com/2008/12/02/hello-elegant-code-readers/#comments Tue, 02 Dec 2008 15:18:27 +0000 Ryan Kelley http://elegantcode.com/2008/12/02/hello-elegant-code-readers/ As Jarod Ferguson already mentioned, I am now part of the Elegant Code team. I must say it is an honor to be invited to join this community and I am very excited about this opportunity. I will still cross-post on my own blog as well as here on elegantcode.com.

I am a pretty easy going guy, so hopefully this opportunity will spur me into posting with more regularity. If anybody has any topics they want me to write about just drop me a line.

One last thing, Thank You to all the Elegant Coders for giving me the invite.

]]> http://elegantcode.com/2008/12/02/hello-elegant-code-readers/feed/ 3 Joining Elegant Code http://elegantcode.com/2008/11/22/joining-elegant-code/?utm_source=rss&utm_medium=rss&utm_campaign=joining-elegant-code http://elegantcode.com/2008/11/22/joining-elegant-code/#comments Sun, 23 Nov 2008 00:52:53 +0000 Guest Blogger http://elegantcode.com/?p=1545 mentioned, i am now part of the Elegant Code team. It's an honor to be invited and i'm obviously very happy with this. All of my posts will still be posted to my own blog, as well as on elegantcode.com. And the NHibernate posts will also continue to be cross posted to NHForge. Now if you'll excuse me, i've got to start writing some posts ;)]]> http://elegantcode.com/2008/11/22/joining-elegant-code/feed/ 2 The New Blogger Toolkit http://elegantcode.com Tue, 15 May 2012 10:00:00 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 Elegant Code » Blogging http://elegantcode.com Tue, 15 May 2012 10:00:00 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 I guess an introduction is in order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/?utm_source=rss&utm_medium=rss&utm_campaign=i-guess-an-introduction-is-in-order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/#comments Sun, 15 Aug 2010 21:50:26 +0000 Andreas Håkansson http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/ Twitter or from my self-titled blog that I have been blogging on up until this point (and might continue doing, haven’t really made up my mind yet what I am going to do with it). However, my real name is Andreas Håkansson and I guess I could describe myself as a nearly 30 year old .NET developer from Sweden, with a passion for pretty much everything in the software engineering / craftsmanship department (hey, why limit yourself to one kind of cake when there’s so much to be had out there!). I am a strong advocator of Open-Source Software and I head the MEF Contrib project, a set of community contributed extensions, tools and samples for the Managed Extensibility Framework, and I have also created the Common Service Factory, a WCF extension that enabled dependency injection in services (it’s a bit dated, but it works like a charm – probably should give it some love as soon as I can find a slice of spare time in my life). Oh yeah, there’s more to me than being a code ninjah – somehow I’ve also managed to get married to my high school sweetheart (12 years since we hooked up and still going strong) and together we have two wonderful boys (3 and 1½ years old – boy do they know how to keep us busy hehe) Well I guess that’s it… now you know a bit about me, and I hope to get to know a bit more about you, the readers of Elegant Code, so please stop by my posts and drop me a line or two. See you there!]]> http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/feed/ 2 What Does Elegant Code Mean to Me? http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/?utm_source=rss&utm_medium=rss&utm_campaign=what-does-elegant-code-mean-to-me http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/#comments Fri, 09 Apr 2010 19:46:38 +0000 John Sonmez http://elegantcode.com/?p=3434 What is elegance? Simply stated. Something that is simple yet effective, delivered with grace. Being simple is not enough. Simple lacking effectiveness is just a waste of time. Simple - Not Effective Simple, but not effective is a foam hammer. You don't want your code to be like a foam hammer. If it can't do what it supposed to do the simplicity just looks like stupidity instead. Effective, but not simple is something that gets thrown away or lamented. It's a Rube Goldberg machine. Rube Goldberg Machine You don't want your code to be like a Rube Goldberg machine either.  Where people look at your code because it is such a spectacle.  You don't want someone to look at your code and immediately think they want to kill you.  Code that evokes murderous rage, tends to get blamed for anything that goes wrong in the system, even if it works perfectly. If you can build something simple and its effective, it still has to be delivered in a graceful way. Consider, the elephant harness... Simple and Effective - Not Graceful Simple?  Yes, it's a box strapped on top of an Elephant, can't get much more simple than that.  Effective?  Yes, looks to me like that elephant will get you where you need to go in that terrain.  Delivered with grace?  Hmm...  Do you want to ride around on an elephant? Even if you nail the first two, with your code, you should make sure it looks and reads good.  No one wants to ride an elephant.  I have seen more than one simple effective design get thrown away because the variables were named things like "cntr" and "banana".

Elegant Code is James Bond

Women love him, men want to be like him and he kills people with a simple sophistication. When people read your code they should think James Bond, not Booger from Revenge of the Nerds. James-Bond Vs. booger
Elegant code to me is code that reads well, does what is is supposed to do and is easy to maintain. Now that I have told you what I think elegant code is, in future posts I will talk more about how to actually write elegant code.

Side Note - Joining Elegant Code

First of all I wanted to publicly thank the other Elegant Coders for inviting me to join their community. I feel honored and esteemed to be joining such a great group of software craftsmen. I also wanted to clear up confusion for anyone who has been following my blog at http://simpleprogrammer.com.  I will still be blogging there, so don't change your RSS feeds, but in addition I will be blogging here at ElegantCode.com.  If you've come here form a link on my personal blog, I encourage you to check out the other excellent bloggers on this site and consider adding Elegant Code to your RSS feed reader.   My personal blog will contain a wider array of topics, but my content here at ElegantCode.com will be centered around the theme of writing elegant code. As always, feel free to email me at john *dot* sonmez *at* gmail.com or follow me on twitter.]]> http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/feed/ 1 Welcome Two New Elegant Coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/?utm_source=rss&utm_medium=rss&utm_campaign=welcome-two-new-elegant-coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/#comments Thu, 15 Oct 2009 19:58:17 +0000 David Starr http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/ I am happy to introduce 2 new Elegant Coders! We are excited to have their contributions to the site and look forward to their wisdom.

Kirstin Juhl

@kirstinj

We are excited to have Kirstin drop wisdom like she has been doing on her current blog: I [heart] Code. From her own bio:

I am a former engineer who writes code. I did Toyota Operating System, Kanban, and Lean in my factories a decade ago, and am fascinated by its use in software development today. You can take the girl out of the factory, but you cannot take the engineer out of the girl, and so I approach everything in life as a problem to solved or optimized. Including software development. I strive to be a craftsman.

I am a mom, and I take lessons from parenthood into my work everyday.

Jason Jarrett

@staxmanade

Jason is a big-time Silverlight maven and the developer behind StatLight, a set of unit testing tools for Silverlight. I knew he was perfect for the tribe when he said, “… and so I added automocking to Unity for Silverlight.”

Yeah. :)

Welcome all.

]]> http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/feed/ 0 FubuMVC From Scratch – Part 4 Persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/?utm_source=rss&utm_medium=rss&utm_campaign=fubumvc-from-scratch-part-4-persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/#comments Wed, 25 Mar 2009 21:22:00 +0000 Ryan Kelley http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/ Previous posts in series:

Persistence is a requirement in virtually every application that we write today, and now the time has come for us to add a persistence model to our FubuMVC app. I know I mentioned moving my samples to the FubuCart source, but I am going to go ahead and implement the persistence piece in the same project the previous articles using, FubuSample. I have also added all the code for this series to the FubuMVC-Contrib project

We will be implementing our persistence model to use NHibernate, Fluent NHibernate, Repository Pattern and UnitOfWork pattern all on top of SQL Express or standard. This will also work for sqllite and other database servers.

Class and Interfaces we have to implement:

  • ISessionSourceConfiguration
  • SQLServerSessionSourceConfiguration
  • IUnitOfWork
  • INHibernateUnitOfWork
  • NHibernateUnitOfWork
  • IRepository
  • NHibernateRepository
  • DomainEntity
  • IDomainQuery
  • FubuSamplePersistenceModel

Note: I put the first two in the list in my Core.Config namespace, and the rest in Core.Persistence

Before we start you probably want to go ahead and add the following references to your core project and Web project

FubuMVC-Persist-Ref

Let’s just work our way down the list and get these files implemented.

ISessionSourceConfiguration

public interface ISessionSourceConfiguration
{
    bool IsNewDatabase { get; }
    ISessionSource CreateSessionSource(PersistenceModel model);
}

SQLServerSessionSourceConfiguration

public class SQLServerSessionSourceConfiguration : ISessionSourceConfiguration
{
    #region Implementation of ISessionSourceConfiguration
 
    public bool IsNewDatabase
    {
        get { return false; }
    }
 
    public ISessionSource CreateSessionSource(PersistenceModel model)
    {
        var properties = GetProperties();
        var source = new SessionSource(properties, model);
 
        create_schema_if_it_does_not_already_exist(source);
 
        return source;
    }
 
    private void create_schema_if_it_does_not_already_exist(ISessionSource source)
    {
        if (IsNewDatabase) source.BuildSchema();
    }
 
    protected IDictionary<string, string> GetProperties()
    {
        MsSqlConfiguration config = MsSqlConfiguration.MsSql2005;
        config.ConnectionString.FromConnectionStringWithKey(“MYDBKEY”);
        config.ShowSql();
        config.UseOuterJoin();
 
        return config.ToProperties();
    }
    #endregion
}

A quick note here: We told SQLServerSessionSourceConfiguration to use a connection string from the app settings file (Web.Config) with a key of “MYDBKEY” This will be important later.

IUnitOfWork

public interface IUnitOfWork : IDisposable
{
    void Initialize();
    void Commit();
    void Rollback();
}

INHibernateUnitOfWork

public interface INHibernateUnitOfWork : IUnitOfWork
{
    ISession CurrentSession { get; }
}

NHibernateUnitOfWork

public class NHibernateUnitOfWork : INHibernateUnitOfWork
{
    private ITransaction _transaction;
    private bool _isDisposed;
    private readonly ISessionSource _source;
    private bool _isInitialized;
 
    public NHibernateUnitOfWork(ISessionSource source)
    {
        _source = source;
    }
 
    public void Initialize()
    {
        should_not_currently_be_disposed();
 
        CurrentSession = _source.CreateSession();
        begin_new_transaction();
 
        _isInitialized = true;
    }
 
    public ISession CurrentSession { get; private set; }
 
    public void Commit()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Commit();
 
        begin_new_transaction();
    }
 
    private void begin_new_transaction()
    {
        if (_transaction != null)
        {
            _transaction.Dispose();
        }
 
        _transaction = CurrentSession.BeginTransaction();
    }
 
    public void Rollback()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Rollback();
 
        begin_new_transaction();
    }
 
    private void should_not_currently_be_disposed()
    {
        if (_isDisposed) throw new ObjectDisposedException(GetType().Name);
    }
 
    private void should_be_initialized_first()
    {
        if (!_isInitialized) throw new InvalidOperationException("Must initialize (call Initialize()) on NHibernateUnitOfWork before commiting or rolling back");
    }
 
    public void Dispose()
    {
        if (_isDisposed || !_isInitialized) return;
 
        _transaction.Dispose();
        CurrentSession.Dispose();
 
        _isDisposed = true;
    }
}

IRepository

public interface IRepository
{
    void Save<ENTITY>(ENTITY entity)
        where ENTITY : DomainEntity;
 
    ENTITY Load<ENTITY>(Guid id)
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>()
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery)
        where ENTITY : DomainEntity;
 
    void Delete<ENTITY>(ENTITY entity);
 
    void DeleteAll<ENTITY>();
}

NHibernateRepository

public class NHibernateRepository : IRepository
{
    private readonly INHibernateUnitOfWork _unitOfWork;
 
    public NHibernateRepository(INHibernateUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public void Save<ENTITY>(ENTITY entity) where ENTITY : DomainEntity
    {
        _unitOfWork.CurrentSession.SaveOrUpdate(entity);
    }
 
    public ENTITY Load<ENTITY>(Guid id) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Load<ENTITY>(id);
    }
 
    public IQueryable<ENTITY> Query<ENTITY>() where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>();
    }
 
    public IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>().Where(whereQuery.Expression);
    }
 
    public void Delete<ENTITY>(ENTITY entity)
    {
        _unitOfWork.CurrentSession.Delete(entity);   
    }
 
    public void DeleteAll<ENTITY>()
    {
        var query = String.Format("from {0}", typeof(ENTITY).Name);
        _unitOfWork.CurrentSession.Delete(query);   
    }
}

DomainEntity

Note: I put both of these classes in my Core.Domain namespace, also XML comments are in Source Repository

public class DomainEntity : IEquatable<DomainEntity>
{
    public virtual Guid ID { get; set; }
 
    public virtual bool Equals(DomainEntity other)
    {
        if (ReferenceEquals(null, other)) return false;
        if (ReferenceEquals(this, other)) return true;
        return other.ID.Equals(ID);
    }
 
    public override bool Equals(object obj)
    {
        if (ReferenceEquals(null, obj)) return false;
        if (ReferenceEquals(this, obj)) return true;
        if (obj.GetType() != GetType()) return false;
        return Equals((DomainEntity)obj);
    }
 
    public override int GetHashCode()
    {
        return ID.GetHashCode();
    }
 
    public static bool operator ==(DomainEntity left, DomainEntity right)
    {
        return Equals(left, right);
    }
 
    public static bool operator !=(DomainEntity left, DomainEntity right)
    {
        return !Equals(left, right);
    }
}

IDomainQuery

public interface IDomainQuery<ENTITY>
    where ENTITY : DomainEntity
{
    Expression<Func<ENTITY, bool>> Expression { get; }
}

FubuSamplePersistenceModel

namespace FubuSample.Core.Domain.Persistence
{
    public class FubuSamplePersistenceModel : PersistenceModel
    {
        public FubuSamplePersistenceModel()
        {
            addMappingsFromThisAssembly();
        }
    }
}

Now that we have all the puzzle pieces in place we need to hook them up and make them do some work. Open up FubuSampleWebRegistry

And add the following code:

protected override void configure()
{
    ForRequestedType<ISessionSourceConfiguration>().AsSingletons()
        .TheDefault.Is.OfConcreteType<SQLServerSessionSourceConfiguration>();
 
 
    ForRequestedType<ISessionSource>().AsSingletons()
        .TheDefault.Is.ConstructedBy(ctx =>
                                     ctx.GetInstance<ISessionSourceConfiguration>()
                                         .CreateSessionSource(new FubuSamplePersistenceModel()));
 
    ForRequestedType<IUnitOfWork>().TheDefault.Is.ConstructedBy(ctx => ctx.GetInstance<INHibernateUnitOfWork>());
 
    ForRequestedType<INHibernateUnitOfWork>().CacheBy(InstanceScope.Hybrid)
        .TheDefault.Is.OfConcreteType<NHibernateUnitOfWork>();
 
    ForRequestedType<IRepository>().TheDefault.Is.OfConcreteType<NHibernateRepository>();
}

With a little luck and all of our mad skills, we should be able to talk to the database now. So we need to plumb our simple product object up to talk to NHibernate. We will do this with a mapping file, and since we are using FluentNHibernate we can do this strongly typed.

Make the following modifications to Product: Extend DomainEntity and get rid of Id Property, it is inherited

public class Product : DomainEntity
{
    public virtual string Name { get; set; }
    public virtual string Description { get; set; }
}

Add mapping file for Product:

namespace FubuSample.Core.Domain.Mapping
{
    public class ProductMap : ClassMap<Product>
    {
        public ProductMap()
        {
            Id(e => e.ID).GeneratedBy.GuidComb();
 
            Map(p => p.Name);
            Map(p => p.Description);
            
        }
    }
}

You may also want to setup your connection string at this point in the Web.Config file, mine looks like this:

<add name="MYDBKEY" connectionString="Data Source=LOCALHOST;initial catalog=FubuSample;Integrated Security=SSPI;" providerName="System.Data.SqlClient" />

I also created an empty database in my local SQL Server instance called “FubuSample” And then I went back to SQLServerSessionSourceConfiguration and changed the value of IsNewDatabase to return true. This will create the schema for the database when the application first runs. There is a multitude of different ways that we can handle this, but this was easy for the tutorial purposes.

Next we will add a behavior to our core project and tell FubuMVC to apply that behavior to all or our ControllerActions.

Create a class named “access_the_database_through_a_unit_of_work” in your Core.Web.Behaviors namespace. The contents will look like this:

public class access_the_database_through_a_unit_of_work : IControllerActionBehavior
{
    private readonly IUnitOfWork _unitOfWork;
 
    public access_the_database_through_a_unit_of_work(IUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public IControllerActionBehavior InsideBehavior { get; set; }
    public IInvocationResult Result { get; set; }
 
    public OUTPUT Invoke<INPUT, OUTPUT>(INPUT input, Func<INPUT, OUTPUT> func)
        where INPUT : class
        where OUTPUT : class
    {
        _unitOfWork.Initialize();
 
        try
        {
            var output = InsideBehavior.Invoke(input, func);
            Result = InsideBehavior.Result;
 
            _unitOfWork.Commit();
 
            return output;
        }
        catch
        {
            _unitOfWork.Rollback();
            throw;
        }
        finally
        {
            _unitOfWork.Dispose();
        }
    }
}

Now to tell FubuMVC what to do, open up Global.asax.cs or your Bootstrapper, wherever you are doing the configuration of FubuMVC. In this project we are doing it in Global.asax.cs Add a new behavior to the section that starts with “x.ByDefault.EveryControllerAction” so it looks like this:

x.ByDefault.EveryControllerAction(d =>
   {
       d.Will<execute_the_result>();
       d.Will<access_the_database_through_a_unit_of_work>();
   });

The last thing we will do is open up HomeController and add this code above the Index action:

private IRepository _repository;
 
public HomeController(IRepository repository)
{
    _repository = repository;
}

I also modified the Index action to go ahead and create some database values before we query for them just so we can test this thing. (I only did this for the tutorial, I swear) So modify the Index action to look like this:

public IndexViewModel Index(IndexSetupViewModel inModel)
{
    var prod1 = new Product {Name = "TestProduct1", Description = "This is a test product"};
 
    _repository.Save(prod1);
 
    var prod2 = new Product {Name = "TestProduct2", Description = "This is a test product"};
 
    _repository.Save(prod2);
 
    var outModel = new IndexViewModel();
 
    var productList = _repository.Query<Product>();
 
    outModel.Products = productList.ToList().Select(x => new ProductDisplay(x));
 
    return outModel;
}

Now with you should be able to run your web app and browse to /home and all this will be executed and you will be on your way to creating a whole bunch of persist able objects for use with your FubuMVC app.

As always, feedback is welcome.

]]> http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/feed/ 9 It’s Official – New Gig started last week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/?utm_source=rss&utm_medium=rss&utm_campaign=its-official-new-gig-started-last-week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/#comments Tue, 24 Feb 2009 19:03:21 +0000 Ryan Kelley http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/ CoachesAid.com. CoachesAid is a High School sports website that is expanding rapidly and it is my task to make this expansion happen as smoothly and as quickly as possible. The past month has been very hectic as I was wrapping up loose ends at my previous engagement. I started my new gig last week, but I have pretty much been building furniture and getting computer and server ready to go. The next few weeks will also be challenging as I start to assemble the team of people that is going to make this all happen. How does this tie into the practice of Elegant Coding? Funny you should ask that, the current infrastructure they are built on is a maintenance nightmare so project number one is to completely redo their entire site infrastructure in ASP.Net, and yes it will be MVC based, but not ASP.Net MVC. I am going to architect and build their new infrastructure from the ground up on FubuMVC. So expect a lot more posts from me on FubuMVC and I may even have questions for you dear reader. Side Note: I just finished deploying to production a small scale site built on FubuMVC, and it ROCKS! There is going to be some stuff that needs to be tweaked out and added to the core, but overall, fully functional MVC framework. I hope I haven’t bored you with too much personal information, but I have to go. (I have several FubuMVC posts stacked up in my queue) -Ryan]]> http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/feed/ 8 Quick 2008 Recap and a few New Years Resolutions http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/?utm_source=rss&utm_medium=rss&utm_campaign=quick-2008-recap-and-a-few-new-years-resolutions http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/#comments Thu, 01 Jan 2009 15:57:06 +0000 Ryan Kelley http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/ Whew, I cannot believe that 2008 is over already, it seems like it just started. 2008 was a great year for me as a developer for several reasons.

Met new People

I was able to meet a ton of new people in 2008, both online through blogs and other communities, and at KaizenConf in Austin. This is probably the single most important thing that happened to me in 2008 because it helped put me into circle of people that share the same thoughts and values about software development that I do.

Alt.Net Introduction

I was also introduced to the Alt.Net movement during 2008. I have been developing software for several years and some of the things I had been doing just didn’t seem quite right, they worked, but they had a smell to them. Enter Alt.Net, this stuff just makes sense. It is smart software development, that revolves around creating highly testable, highly maintainable code that follows the SOLID design principles. I have come to realize that if you just ask yourself “How does this proposed solution adhere to the SOLID principles” you will write much more elegant code.

KaizenConf Open Spaces Conference

This was my first open spaces conference and I didn’t know what to expect but I came away with the feeling that this was the best conference I had ever been to. KaizenConf helped fuel my fire for continuing with more Alt.Net stuff, working on Lean Software Development and KanBan methods, and staying involved with the community. It even spurred me to start blogging more frequently about these topics.

Some 2009 Resolutions

I have a few resolutions I am going to make for the new year, some are computer related, some are not.

  • Blog More – I am targeting 52 blog posts in 2009, that is a little more than double from 2008 and is only 1 per week.
  • Fish more, I love fly fishing, just need to make more time
    • Fly Fish for Bass – talk about fun!
  • Write Elegant Code – I am staying committed to SOLID principles, testability and maintainable code.
  • Learn more about Asp.Net – Especially MVC stuff, I have been doing WinForms development for the past 4 years, so I am looking forward to this one.
  • Learn a new Programming Language – Everybody should do this every year.

I am going to stop there, I don’t want to set any unrealistic expectations for myself during the year. I think all of these are very attainable and I hope that my list has spurred some inner resolution making within you to go out and commit to something new in 2009.

]]> http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/feed/ 2 Hello Elegant Code Readers http://elegantcode.com/2008/12/02/hello-elegant-code-readers/?utm_source=rss&utm_medium=rss&utm_campaign=hello-elegant-code-readers http://elegantcode.com/2008/12/02/hello-elegant-code-readers/#comments Tue, 02 Dec 2008 15:18:27 +0000 Ryan Kelley http://elegantcode.com/2008/12/02/hello-elegant-code-readers/ As Jarod Ferguson already mentioned, I am now part of the Elegant Code team. I must say it is an honor to be invited to join this community and I am very excited about this opportunity. I will still cross-post on my own blog as well as here on elegantcode.com.

I am a pretty easy going guy, so hopefully this opportunity will spur me into posting with more regularity. If anybody has any topics they want me to write about just drop me a line.

One last thing, Thank You to all the Elegant Coders for giving me the invite.

]]> http://elegantcode.com/2008/12/02/hello-elegant-code-readers/feed/ 3 Joining Elegant Code http://elegantcode.com/2008/11/22/joining-elegant-code/?utm_source=rss&utm_medium=rss&utm_campaign=joining-elegant-code http://elegantcode.com/2008/11/22/joining-elegant-code/#comments Sun, 23 Nov 2008 00:52:53 +0000 Guest Blogger http://elegantcode.com/?p=1545 mentioned, i am now part of the Elegant Code team. It's an honor to be invited and i'm obviously very happy with this. All of my posts will still be posted to my own blog, as well as on elegantcode.com. And the NHibernate posts will also continue to be cross posted to NHForge. Now if you'll excuse me, i've got to start writing some posts ;)]]> http://elegantcode.com/2008/11/22/joining-elegant-code/feed/ 2 The New Blogger Toolkit http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/?utm_source=rss&utm_medium=rss&utm_campaign=i-guess-an-introduction-is-in-order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/#comments Sun, 15 Aug 2010 21:50:26 +0000 Andreas Håkansson http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/ Twitter or from my self-titled blog that I have been blogging on up until this point (and might continue doing, haven’t really made up my mind yet what I am going to do with it). However, my real name is Andreas Håkansson and I guess I could describe myself as a nearly 30 year old .NET developer from Sweden, with a passion for pretty much everything in the software engineering / craftsmanship department (hey, why limit yourself to one kind of cake when there’s so much to be had out there!). I am a strong advocator of Open-Source Software and I head the MEF Contrib project, a set of community contributed extensions, tools and samples for the Managed Extensibility Framework, and I have also created the Common Service Factory, a WCF extension that enabled dependency injection in services (it’s a bit dated, but it works like a charm – probably should give it some love as soon as I can find a slice of spare time in my life). Oh yeah, there’s more to me than being a code ninjah – somehow I’ve also managed to get married to my high school sweetheart (12 years since we hooked up and still going strong) and together we have two wonderful boys (3 and 1½ years old – boy do they know how to keep us busy hehe) Well I guess that’s it… now you know a bit about me, and I hope to get to know a bit more about you, the readers of Elegant Code, so please stop by my posts and drop me a line or two. See you there!]]> http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/feed/ 2 Elegant Code » Blogging http://elegantcode.com Tue, 15 May 2012 10:00:00 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 I guess an introduction is in order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/?utm_source=rss&utm_medium=rss&utm_campaign=i-guess-an-introduction-is-in-order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/#comments Sun, 15 Aug 2010 21:50:26 +0000 Andreas Håkansson http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/ Twitter or from my self-titled blog that I have been blogging on up until this point (and might continue doing, haven’t really made up my mind yet what I am going to do with it). However, my real name is Andreas Håkansson and I guess I could describe myself as a nearly 30 year old .NET developer from Sweden, with a passion for pretty much everything in the software engineering / craftsmanship department (hey, why limit yourself to one kind of cake when there’s so much to be had out there!). I am a strong advocator of Open-Source Software and I head the MEF Contrib project, a set of community contributed extensions, tools and samples for the Managed Extensibility Framework, and I have also created the Common Service Factory, a WCF extension that enabled dependency injection in services (it’s a bit dated, but it works like a charm – probably should give it some love as soon as I can find a slice of spare time in my life). Oh yeah, there’s more to me than being a code ninjah – somehow I’ve also managed to get married to my high school sweetheart (12 years since we hooked up and still going strong) and together we have two wonderful boys (3 and 1½ years old – boy do they know how to keep us busy hehe) Well I guess that’s it… now you know a bit about me, and I hope to get to know a bit more about you, the readers of Elegant Code, so please stop by my posts and drop me a line or two. See you there!]]> http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/feed/ 2 What Does Elegant Code Mean to Me? http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/?utm_source=rss&utm_medium=rss&utm_campaign=what-does-elegant-code-mean-to-me http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/#comments Fri, 09 Apr 2010 19:46:38 +0000 John Sonmez http://elegantcode.com/?p=3434 What is elegance? Simply stated. Something that is simple yet effective, delivered with grace. Being simple is not enough. Simple lacking effectiveness is just a waste of time. Simple - Not Effective Simple, but not effective is a foam hammer. You don't want your code to be like a foam hammer. If it can't do what it supposed to do the simplicity just looks like stupidity instead. Effective, but not simple is something that gets thrown away or lamented. It's a Rube Goldberg machine. Rube Goldberg Machine You don't want your code to be like a Rube Goldberg machine either.  Where people look at your code because it is such a spectacle.  You don't want someone to look at your code and immediately think they want to kill you.  Code that evokes murderous rage, tends to get blamed for anything that goes wrong in the system, even if it works perfectly. If you can build something simple and its effective, it still has to be delivered in a graceful way. Consider, the elephant harness... Simple and Effective - Not Graceful Simple?  Yes, it's a box strapped on top of an Elephant, can't get much more simple than that.  Effective?  Yes, looks to me like that elephant will get you where you need to go in that terrain.  Delivered with grace?  Hmm...  Do you want to ride around on an elephant? Even if you nail the first two, with your code, you should make sure it looks and reads good.  No one wants to ride an elephant.  I have seen more than one simple effective design get thrown away because the variables were named things like "cntr" and "banana".

Elegant Code is James Bond

Women love him, men want to be like him and he kills people with a simple sophistication. When people read your code they should think James Bond, not Booger from Revenge of the Nerds. James-Bond Vs. booger
Elegant code to me is code that reads well, does what is is supposed to do and is easy to maintain. Now that I have told you what I think elegant code is, in future posts I will talk more about how to actually write elegant code.

Side Note - Joining Elegant Code

First of all I wanted to publicly thank the other Elegant Coders for inviting me to join their community. I feel honored and esteemed to be joining such a great group of software craftsmen. I also wanted to clear up confusion for anyone who has been following my blog at http://simpleprogrammer.com.  I will still be blogging there, so don't change your RSS feeds, but in addition I will be blogging here at ElegantCode.com.  If you've come here form a link on my personal blog, I encourage you to check out the other excellent bloggers on this site and consider adding Elegant Code to your RSS feed reader.   My personal blog will contain a wider array of topics, but my content here at ElegantCode.com will be centered around the theme of writing elegant code. As always, feel free to email me at john *dot* sonmez *at* gmail.com or follow me on twitter.]]> http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/feed/ 1 Welcome Two New Elegant Coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/?utm_source=rss&utm_medium=rss&utm_campaign=welcome-two-new-elegant-coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/#comments Thu, 15 Oct 2009 19:58:17 +0000 David Starr http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/ I am happy to introduce 2 new Elegant Coders! We are excited to have their contributions to the site and look forward to their wisdom.

Kirstin Juhl

@kirstinj

We are excited to have Kirstin drop wisdom like she has been doing on her current blog: I [heart] Code. From her own bio:

I am a former engineer who writes code. I did Toyota Operating System, Kanban, and Lean in my factories a decade ago, and am fascinated by its use in software development today. You can take the girl out of the factory, but you cannot take the engineer out of the girl, and so I approach everything in life as a problem to solved or optimized. Including software development. I strive to be a craftsman.

I am a mom, and I take lessons from parenthood into my work everyday.

Jason Jarrett

@staxmanade

Jason is a big-time Silverlight maven and the developer behind StatLight, a set of unit testing tools for Silverlight. I knew he was perfect for the tribe when he said, “… and so I added automocking to Unity for Silverlight.”

Yeah. :)

Welcome all.

]]> http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/feed/ 0 FubuMVC From Scratch – Part 4 Persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/?utm_source=rss&utm_medium=rss&utm_campaign=fubumvc-from-scratch-part-4-persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/#comments Wed, 25 Mar 2009 21:22:00 +0000 Ryan Kelley http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/ Previous posts in series:

Persistence is a requirement in virtually every application that we write today, and now the time has come for us to add a persistence model to our FubuMVC app. I know I mentioned moving my samples to the FubuCart source, but I am going to go ahead and implement the persistence piece in the same project the previous articles using, FubuSample. I have also added all the code for this series to the FubuMVC-Contrib project

We will be implementing our persistence model to use NHibernate, Fluent NHibernate, Repository Pattern and UnitOfWork pattern all on top of SQL Express or standard. This will also work for sqllite and other database servers.

Class and Interfaces we have to implement:

  • ISessionSourceConfiguration
  • SQLServerSessionSourceConfiguration
  • IUnitOfWork
  • INHibernateUnitOfWork
  • NHibernateUnitOfWork
  • IRepository
  • NHibernateRepository
  • DomainEntity
  • IDomainQuery
  • FubuSamplePersistenceModel

Note: I put the first two in the list in my Core.Config namespace, and the rest in Core.Persistence

Before we start you probably want to go ahead and add the following references to your core project and Web project

FubuMVC-Persist-Ref

Let’s just work our way down the list and get these files implemented.

ISessionSourceConfiguration

public interface ISessionSourceConfiguration
{
    bool IsNewDatabase { get; }
    ISessionSource CreateSessionSource(PersistenceModel model);
}

SQLServerSessionSourceConfiguration

public class SQLServerSessionSourceConfiguration : ISessionSourceConfiguration
{
    #region Implementation of ISessionSourceConfiguration
 
    public bool IsNewDatabase
    {
        get { return false; }
    }
 
    public ISessionSource CreateSessionSource(PersistenceModel model)
    {
        var properties = GetProperties();
        var source = new SessionSource(properties, model);
 
        create_schema_if_it_does_not_already_exist(source);
 
        return source;
    }
 
    private void create_schema_if_it_does_not_already_exist(ISessionSource source)
    {
        if (IsNewDatabase) source.BuildSchema();
    }
 
    protected IDictionary<string, string> GetProperties()
    {
        MsSqlConfiguration config = MsSqlConfiguration.MsSql2005;
        config.ConnectionString.FromConnectionStringWithKey(“MYDBKEY”);
        config.ShowSql();
        config.UseOuterJoin();
 
        return config.ToProperties();
    }
    #endregion
}

A quick note here: We told SQLServerSessionSourceConfiguration to use a connection string from the app settings file (Web.Config) with a key of “MYDBKEY” This will be important later.

IUnitOfWork

public interface IUnitOfWork : IDisposable
{
    void Initialize();
    void Commit();
    void Rollback();
}

INHibernateUnitOfWork

public interface INHibernateUnitOfWork : IUnitOfWork
{
    ISession CurrentSession { get; }
}

NHibernateUnitOfWork

public class NHibernateUnitOfWork : INHibernateUnitOfWork
{
    private ITransaction _transaction;
    private bool _isDisposed;
    private readonly ISessionSource _source;
    private bool _isInitialized;
 
    public NHibernateUnitOfWork(ISessionSource source)
    {
        _source = source;
    }
 
    public void Initialize()
    {
        should_not_currently_be_disposed();
 
        CurrentSession = _source.CreateSession();
        begin_new_transaction();
 
        _isInitialized = true;
    }
 
    public ISession CurrentSession { get; private set; }
 
    public void Commit()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Commit();
 
        begin_new_transaction();
    }
 
    private void begin_new_transaction()
    {
        if (_transaction != null)
        {
            _transaction.Dispose();
        }
 
        _transaction = CurrentSession.BeginTransaction();
    }
 
    public void Rollback()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Rollback();
 
        begin_new_transaction();
    }
 
    private void should_not_currently_be_disposed()
    {
        if (_isDisposed) throw new ObjectDisposedException(GetType().Name);
    }
 
    private void should_be_initialized_first()
    {
        if (!_isInitialized) throw new InvalidOperationException("Must initialize (call Initialize()) on NHibernateUnitOfWork before commiting or rolling back");
    }
 
    public void Dispose()
    {
        if (_isDisposed || !_isInitialized) return;
 
        _transaction.Dispose();
        CurrentSession.Dispose();
 
        _isDisposed = true;
    }
}

IRepository

public interface IRepository
{
    void Save<ENTITY>(ENTITY entity)
        where ENTITY : DomainEntity;
 
    ENTITY Load<ENTITY>(Guid id)
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>()
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery)
        where ENTITY : DomainEntity;
 
    void Delete<ENTITY>(ENTITY entity);
 
    void DeleteAll<ENTITY>();
}

NHibernateRepository

public class NHibernateRepository : IRepository
{
    private readonly INHibernateUnitOfWork _unitOfWork;
 
    public NHibernateRepository(INHibernateUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public void Save<ENTITY>(ENTITY entity) where ENTITY : DomainEntity
    {
        _unitOfWork.CurrentSession.SaveOrUpdate(entity);
    }
 
    public ENTITY Load<ENTITY>(Guid id) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Load<ENTITY>(id);
    }
 
    public IQueryable<ENTITY> Query<ENTITY>() where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>();
    }
 
    public IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>().Where(whereQuery.Expression);
    }
 
    public void Delete<ENTITY>(ENTITY entity)
    {
        _unitOfWork.CurrentSession.Delete(entity);   
    }
 
    public void DeleteAll<ENTITY>()
    {
        var query = String.Format("from {0}", typeof(ENTITY).Name);
        _unitOfWork.CurrentSession.Delete(query);   
    }
}

DomainEntity

Note: I put both of these classes in my Core.Domain namespace, also XML comments are in Source Repository

public class DomainEntity : IEquatable<DomainEntity>
{
    public virtual Guid ID { get; set; }
 
    public virtual bool Equals(DomainEntity other)
    {
        if (ReferenceEquals(null, other)) return false;
        if (ReferenceEquals(this, other)) return true;
        return other.ID.Equals(ID);
    }
 
    public override bool Equals(object obj)
    {
        if (ReferenceEquals(null, obj)) return false;
        if (ReferenceEquals(this, obj)) return true;
        if (obj.GetType() != GetType()) return false;
        return Equals((DomainEntity)obj);
    }
 
    public override int GetHashCode()
    {
        return ID.GetHashCode();
    }
 
    public static bool operator ==(DomainEntity left, DomainEntity right)
    {
        return Equals(left, right);
    }
 
    public static bool operator !=(DomainEntity left, DomainEntity right)
    {
        return !Equals(left, right);
    }
}

IDomainQuery

public interface IDomainQuery<ENTITY>
    where ENTITY : DomainEntity
{
    Expression<Func<ENTITY, bool>> Expression { get; }
}

FubuSamplePersistenceModel

namespace FubuSample.Core.Domain.Persistence
{
    public class FubuSamplePersistenceModel : PersistenceModel
    {
        public FubuSamplePersistenceModel()
        {
            addMappingsFromThisAssembly();
        }
    }
}

Now that we have all the puzzle pieces in place we need to hook them up and make them do some work. Open up FubuSampleWebRegistry

And add the following code:

protected override void configure()
{
    ForRequestedType<ISessionSourceConfiguration>().AsSingletons()
        .TheDefault.Is.OfConcreteType<SQLServerSessionSourceConfiguration>();
 
 
    ForRequestedType<ISessionSource>().AsSingletons()
        .TheDefault.Is.ConstructedBy(ctx =>
                                     ctx.GetInstance<ISessionSourceConfiguration>()
                                         .CreateSessionSource(new FubuSamplePersistenceModel()));
 
    ForRequestedType<IUnitOfWork>().TheDefault.Is.ConstructedBy(ctx => ctx.GetInstance<INHibernateUnitOfWork>());
 
    ForRequestedType<INHibernateUnitOfWork>().CacheBy(InstanceScope.Hybrid)
        .TheDefault.Is.OfConcreteType<NHibernateUnitOfWork>();
 
    ForRequestedType<IRepository>().TheDefault.Is.OfConcreteType<NHibernateRepository>();
}

With a little luck and all of our mad skills, we should be able to talk to the database now. So we need to plumb our simple product object up to talk to NHibernate. We will do this with a mapping file, and since we are using FluentNHibernate we can do this strongly typed.

Make the following modifications to Product: Extend DomainEntity and get rid of Id Property, it is inherited

public class Product : DomainEntity
{
    public virtual string Name { get; set; }
    public virtual string Description { get; set; }
}

Add mapping file for Product:

namespace FubuSample.Core.Domain.Mapping
{
    public class ProductMap : ClassMap<Product>
    {
        public ProductMap()
        {
            Id(e => e.ID).GeneratedBy.GuidComb();
 
            Map(p => p.Name);
            Map(p => p.Description);
            
        }
    }
}

You may also want to setup your connection string at this point in the Web.Config file, mine looks like this:

<add name="MYDBKEY" connectionString="Data Source=LOCALHOST;initial catalog=FubuSample;Integrated Security=SSPI;" providerName="System.Data.SqlClient" />

I also created an empty database in my local SQL Server instance called “FubuSample” And then I went back to SQLServerSessionSourceConfiguration and changed the value of IsNewDatabase to return true. This will create the schema for the database when the application first runs. There is a multitude of different ways that we can handle this, but this was easy for the tutorial purposes.

Next we will add a behavior to our core project and tell FubuMVC to apply that behavior to all or our ControllerActions.

Create a class named “access_the_database_through_a_unit_of_work” in your Core.Web.Behaviors namespace. The contents will look like this:

public class access_the_database_through_a_unit_of_work : IControllerActionBehavior
{
    private readonly IUnitOfWork _unitOfWork;
 
    public access_the_database_through_a_unit_of_work(IUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public IControllerActionBehavior InsideBehavior { get; set; }
    public IInvocationResult Result { get; set; }
 
    public OUTPUT Invoke<INPUT, OUTPUT>(INPUT input, Func<INPUT, OUTPUT> func)
        where INPUT : class
        where OUTPUT : class
    {
        _unitOfWork.Initialize();
 
        try
        {
            var output = InsideBehavior.Invoke(input, func);
            Result = InsideBehavior.Result;
 
            _unitOfWork.Commit();
 
            return output;
        }
        catch
        {
            _unitOfWork.Rollback();
            throw;
        }
        finally
        {
            _unitOfWork.Dispose();
        }
    }
}

Now to tell FubuMVC what to do, open up Global.asax.cs or your Bootstrapper, wherever you are doing the configuration of FubuMVC. In this project we are doing it in Global.asax.cs Add a new behavior to the section that starts with “x.ByDefault.EveryControllerAction” so it looks like this:

x.ByDefault.EveryControllerAction(d =>
   {
       d.Will<execute_the_result>();
       d.Will<access_the_database_through_a_unit_of_work>();
   });

The last thing we will do is open up HomeController and add this code above the Index action:

private IRepository _repository;
 
public HomeController(IRepository repository)
{
    _repository = repository;
}

I also modified the Index action to go ahead and create some database values before we query for them just so we can test this thing. (I only did this for the tutorial, I swear) So modify the Index action to look like this:

public IndexViewModel Index(IndexSetupViewModel inModel)
{
    var prod1 = new Product {Name = "TestProduct1", Description = "This is a test product"};
 
    _repository.Save(prod1);
 
    var prod2 = new Product {Name = "TestProduct2", Description = "This is a test product"};
 
    _repository.Save(prod2);
 
    var outModel = new IndexViewModel();
 
    var productList = _repository.Query<Product>();
 
    outModel.Products = productList.ToList().Select(x => new ProductDisplay(x));
 
    return outModel;
}

Now with you should be able to run your web app and browse to /home and all this will be executed and you will be on your way to creating a whole bunch of persist able objects for use with your FubuMVC app.

As always, feedback is welcome.

]]> http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/feed/ 9 It’s Official – New Gig started last week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/?utm_source=rss&utm_medium=rss&utm_campaign=its-official-new-gig-started-last-week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/#comments Tue, 24 Feb 2009 19:03:21 +0000 Ryan Kelley http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/ CoachesAid.com. CoachesAid is a High School sports website that is expanding rapidly and it is my task to make this expansion happen as smoothly and as quickly as possible. The past month has been very hectic as I was wrapping up loose ends at my previous engagement. I started my new gig last week, but I have pretty much been building furniture and getting computer and server ready to go. The next few weeks will also be challenging as I start to assemble the team of people that is going to make this all happen. How does this tie into the practice of Elegant Coding? Funny you should ask that, the current infrastructure they are built on is a maintenance nightmare so project number one is to completely redo their entire site infrastructure in ASP.Net, and yes it will be MVC based, but not ASP.Net MVC. I am going to architect and build their new infrastructure from the ground up on FubuMVC. So expect a lot more posts from me on FubuMVC and I may even have questions for you dear reader. Side Note: I just finished deploying to production a small scale site built on FubuMVC, and it ROCKS! There is going to be some stuff that needs to be tweaked out and added to the core, but overall, fully functional MVC framework. I hope I haven’t bored you with too much personal information, but I have to go. (I have several FubuMVC posts stacked up in my queue) -Ryan]]> http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/feed/ 8 Quick 2008 Recap and a few New Years Resolutions http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/?utm_source=rss&utm_medium=rss&utm_campaign=quick-2008-recap-and-a-few-new-years-resolutions http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/#comments Thu, 01 Jan 2009 15:57:06 +0000 Ryan Kelley http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/ Whew, I cannot believe that 2008 is over already, it seems like it just started. 2008 was a great year for me as a developer for several reasons.

Met new People

I was able to meet a ton of new people in 2008, both online through blogs and other communities, and at KaizenConf in Austin. This is probably the single most important thing that happened to me in 2008 because it helped put me into circle of people that share the same thoughts and values about software development that I do.

Alt.Net Introduction

I was also introduced to the Alt.Net movement during 2008. I have been developing software for several years and some of the things I had been doing just didn’t seem quite right, they worked, but they had a smell to them. Enter Alt.Net, this stuff just makes sense. It is smart software development, that revolves around creating highly testable, highly maintainable code that follows the SOLID design principles. I have come to realize that if you just ask yourself “How does this proposed solution adhere to the SOLID principles” you will write much more elegant code.

KaizenConf Open Spaces Conference

This was my first open spaces conference and I didn’t know what to expect but I came away with the feeling that this was the best conference I had ever been to. KaizenConf helped fuel my fire for continuing with more Alt.Net stuff, working on Lean Software Development and KanBan methods, and staying involved with the community. It even spurred me to start blogging more frequently about these topics.

Some 2009 Resolutions

I have a few resolutions I am going to make for the new year, some are computer related, some are not.

  • Blog More – I am targeting 52 blog posts in 2009, that is a little more than double from 2008 and is only 1 per week.
  • Fish more, I love fly fishing, just need to make more time
    • Fly Fish for Bass – talk about fun!
  • Write Elegant Code – I am staying committed to SOLID principles, testability and maintainable code.
  • Learn more about Asp.Net – Especially MVC stuff, I have been doing WinForms development for the past 4 years, so I am looking forward to this one.
  • Learn a new Programming Language – Everybody should do this every year.

I am going to stop there, I don’t want to set any unrealistic expectations for myself during the year. I think all of these are very attainable and I hope that my list has spurred some inner resolution making within you to go out and commit to something new in 2009.

]]> http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/feed/ 2 Hello Elegant Code Readers http://elegantcode.com/2008/12/02/hello-elegant-code-readers/?utm_source=rss&utm_medium=rss&utm_campaign=hello-elegant-code-readers http://elegantcode.com/2008/12/02/hello-elegant-code-readers/#comments Tue, 02 Dec 2008 15:18:27 +0000 Ryan Kelley http://elegantcode.com/2008/12/02/hello-elegant-code-readers/ As Jarod Ferguson already mentioned, I am now part of the Elegant Code team. I must say it is an honor to be invited to join this community and I am very excited about this opportunity. I will still cross-post on my own blog as well as here on elegantcode.com.

I am a pretty easy going guy, so hopefully this opportunity will spur me into posting with more regularity. If anybody has any topics they want me to write about just drop me a line.

One last thing, Thank You to all the Elegant Coders for giving me the invite.

]]> http://elegantcode.com/2008/12/02/hello-elegant-code-readers/feed/ 3 Joining Elegant Code http://elegantcode.com/2008/11/22/joining-elegant-code/?utm_source=rss&utm_medium=rss&utm_campaign=joining-elegant-code http://elegantcode.com/2008/11/22/joining-elegant-code/#comments Sun, 23 Nov 2008 00:52:53 +0000 Guest Blogger http://elegantcode.com/?p=1545 mentioned, i am now part of the Elegant Code team. It's an honor to be invited and i'm obviously very happy with this. All of my posts will still be posted to my own blog, as well as on elegantcode.com. And the NHibernate posts will also continue to be cross posted to NHForge. Now if you'll excuse me, i've got to start writing some posts ;)]]> http://elegantcode.com/2008/11/22/joining-elegant-code/feed/ 2 The New Blogger Toolkit http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/?utm_source=rss&utm_medium=rss&utm_campaign=what-does-elegant-code-mean-to-me http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/#comments Fri, 09 Apr 2010 19:46:38 +0000 John Sonmez http://elegantcode.com/?p=3434 What is elegance? Simply stated. Something that is simple yet effective, delivered with grace. Being simple is not enough. Simple lacking effectiveness is just a waste of time. Simple - Not Effective Simple, but not effective is a foam hammer. You don't want your code to be like a foam hammer. If it can't do what it supposed to do the simplicity just looks like stupidity instead. Effective, but not simple is something that gets thrown away or lamented. It's a Rube Goldberg machine. Rube Goldberg Machine You don't want your code to be like a Rube Goldberg machine either.  Where people look at your code because it is such a spectacle.  You don't want someone to look at your code and immediately think they want to kill you.  Code that evokes murderous rage, tends to get blamed for anything that goes wrong in the system, even if it works perfectly. If you can build something simple and its effective, it still has to be delivered in a graceful way. Consider, the elephant harness... Simple and Effective - Not Graceful Simple?  Yes, it's a box strapped on top of an Elephant, can't get much more simple than that.  Effective?  Yes, looks to me like that elephant will get you where you need to go in that terrain.  Delivered with grace?  Hmm...  Do you want to ride around on an elephant? Even if you nail the first two, with your code, you should make sure it looks and reads good.  No one wants to ride an elephant.  I have seen more than one simple effective design get thrown away because the variables were named things like "cntr" and "banana".

Elegant Code is James Bond

Women love him, men want to be like him and he kills people with a simple sophistication. When people read your code they should think James Bond, not Booger from Revenge of the Nerds. James-Bond Vs. booger
Elegant code to me is code that reads well, does what is is supposed to do and is easy to maintain. Now that I have told you what I think elegant code is, in future posts I will talk more about how to actually write elegant code.

Side Note - Joining Elegant Code

First of all I wanted to publicly thank the other Elegant Coders for inviting me to join their community. I feel honored and esteemed to be joining such a great group of software craftsmen. I also wanted to clear up confusion for anyone who has been following my blog at http://simpleprogrammer.com.  I will still be blogging there, so don't change your RSS feeds, but in addition I will be blogging here at ElegantCode.com.  If you've come here form a link on my personal blog, I encourage you to check out the other excellent bloggers on this site and consider adding Elegant Code to your RSS feed reader.   My personal blog will contain a wider array of topics, but my content here at ElegantCode.com will be centered around the theme of writing elegant code. As always, feel free to email me at john *dot* sonmez *at* gmail.com or follow me on twitter.]]> http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/feed/ 1 Elegant Code » Blogging http://elegantcode.com Tue, 15 May 2012 10:00:00 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 I guess an introduction is in order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/?utm_source=rss&utm_medium=rss&utm_campaign=i-guess-an-introduction-is-in-order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/#comments Sun, 15 Aug 2010 21:50:26 +0000 Andreas Håkansson http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/ Twitter or from my self-titled blog that I have been blogging on up until this point (and might continue doing, haven’t really made up my mind yet what I am going to do with it). However, my real name is Andreas Håkansson and I guess I could describe myself as a nearly 30 year old .NET developer from Sweden, with a passion for pretty much everything in the software engineering / craftsmanship department (hey, why limit yourself to one kind of cake when there’s so much to be had out there!). I am a strong advocator of Open-Source Software and I head the MEF Contrib project, a set of community contributed extensions, tools and samples for the Managed Extensibility Framework, and I have also created the Common Service Factory, a WCF extension that enabled dependency injection in services (it’s a bit dated, but it works like a charm – probably should give it some love as soon as I can find a slice of spare time in my life). Oh yeah, there’s more to me than being a code ninjah – somehow I’ve also managed to get married to my high school sweetheart (12 years since we hooked up and still going strong) and together we have two wonderful boys (3 and 1½ years old – boy do they know how to keep us busy hehe) Well I guess that’s it… now you know a bit about me, and I hope to get to know a bit more about you, the readers of Elegant Code, so please stop by my posts and drop me a line or two. See you there!]]> http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/feed/ 2 What Does Elegant Code Mean to Me? http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/?utm_source=rss&utm_medium=rss&utm_campaign=what-does-elegant-code-mean-to-me http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/#comments Fri, 09 Apr 2010 19:46:38 +0000 John Sonmez http://elegantcode.com/?p=3434 What is elegance? Simply stated. Something that is simple yet effective, delivered with grace. Being simple is not enough. Simple lacking effectiveness is just a waste of time. Simple - Not Effective Simple, but not effective is a foam hammer. You don't want your code to be like a foam hammer. If it can't do what it supposed to do the simplicity just looks like stupidity instead. Effective, but not simple is something that gets thrown away or lamented. It's a Rube Goldberg machine. Rube Goldberg Machine You don't want your code to be like a Rube Goldberg machine either.  Where people look at your code because it is such a spectacle.  You don't want someone to look at your code and immediately think they want to kill you.  Code that evokes murderous rage, tends to get blamed for anything that goes wrong in the system, even if it works perfectly. If you can build something simple and its effective, it still has to be delivered in a graceful way. Consider, the elephant harness... Simple and Effective - Not Graceful Simple?  Yes, it's a box strapped on top of an Elephant, can't get much more simple than that.  Effective?  Yes, looks to me like that elephant will get you where you need to go in that terrain.  Delivered with grace?  Hmm...  Do you want to ride around on an elephant? Even if you nail the first two, with your code, you should make sure it looks and reads good.  No one wants to ride an elephant.  I have seen more than one simple effective design get thrown away because the variables were named things like "cntr" and "banana".

Elegant Code is James Bond

Women love him, men want to be like him and he kills people with a simple sophistication. When people read your code they should think James Bond, not Booger from Revenge of the Nerds. James-Bond Vs. booger
Elegant code to me is code that reads well, does what is is supposed to do and is easy to maintain. Now that I have told you what I think elegant code is, in future posts I will talk more about how to actually write elegant code.

Side Note - Joining Elegant Code

First of all I wanted to publicly thank the other Elegant Coders for inviting me to join their community. I feel honored and esteemed to be joining such a great group of software craftsmen. I also wanted to clear up confusion for anyone who has been following my blog at http://simpleprogrammer.com.  I will still be blogging there, so don't change your RSS feeds, but in addition I will be blogging here at ElegantCode.com.  If you've come here form a link on my personal blog, I encourage you to check out the other excellent bloggers on this site and consider adding Elegant Code to your RSS feed reader.   My personal blog will contain a wider array of topics, but my content here at ElegantCode.com will be centered around the theme of writing elegant code. As always, feel free to email me at john *dot* sonmez *at* gmail.com or follow me on twitter.]]> http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/feed/ 1 Welcome Two New Elegant Coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/?utm_source=rss&utm_medium=rss&utm_campaign=welcome-two-new-elegant-coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/#comments Thu, 15 Oct 2009 19:58:17 +0000 David Starr http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/ I am happy to introduce 2 new Elegant Coders! We are excited to have their contributions to the site and look forward to their wisdom.

Kirstin Juhl

@kirstinj

We are excited to have Kirstin drop wisdom like she has been doing on her current blog: I [heart] Code. From her own bio:

I am a former engineer who writes code. I did Toyota Operating System, Kanban, and Lean in my factories a decade ago, and am fascinated by its use in software development today. You can take the girl out of the factory, but you cannot take the engineer out of the girl, and so I approach everything in life as a problem to solved or optimized. Including software development. I strive to be a craftsman.

I am a mom, and I take lessons from parenthood into my work everyday.

Jason Jarrett

@staxmanade

Jason is a big-time Silverlight maven and the developer behind StatLight, a set of unit testing tools for Silverlight. I knew he was perfect for the tribe when he said, “… and so I added automocking to Unity for Silverlight.”

Yeah. :)

Welcome all.

]]> http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/feed/ 0 FubuMVC From Scratch – Part 4 Persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/?utm_source=rss&utm_medium=rss&utm_campaign=fubumvc-from-scratch-part-4-persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/#comments Wed, 25 Mar 2009 21:22:00 +0000 Ryan Kelley http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/ Previous posts in series:

Persistence is a requirement in virtually every application that we write today, and now the time has come for us to add a persistence model to our FubuMVC app. I know I mentioned moving my samples to the FubuCart source, but I am going to go ahead and implement the persistence piece in the same project the previous articles using, FubuSample. I have also added all the code for this series to the FubuMVC-Contrib project

We will be implementing our persistence model to use NHibernate, Fluent NHibernate, Repository Pattern and UnitOfWork pattern all on top of SQL Express or standard. This will also work for sqllite and other database servers.

Class and Interfaces we have to implement:

  • ISessionSourceConfiguration
  • SQLServerSessionSourceConfiguration
  • IUnitOfWork
  • INHibernateUnitOfWork
  • NHibernateUnitOfWork
  • IRepository
  • NHibernateRepository
  • DomainEntity
  • IDomainQuery
  • FubuSamplePersistenceModel

Note: I put the first two in the list in my Core.Config namespace, and the rest in Core.Persistence

Before we start you probably want to go ahead and add the following references to your core project and Web project

FubuMVC-Persist-Ref

Let’s just work our way down the list and get these files implemented.

ISessionSourceConfiguration

public interface ISessionSourceConfiguration
{
    bool IsNewDatabase { get; }
    ISessionSource CreateSessionSource(PersistenceModel model);
}

SQLServerSessionSourceConfiguration

public class SQLServerSessionSourceConfiguration : ISessionSourceConfiguration
{
    #region Implementation of ISessionSourceConfiguration
 
    public bool IsNewDatabase
    {
        get { return false; }
    }
 
    public ISessionSource CreateSessionSource(PersistenceModel model)
    {
        var properties = GetProperties();
        var source = new SessionSource(properties, model);
 
        create_schema_if_it_does_not_already_exist(source);
 
        return source;
    }
 
    private void create_schema_if_it_does_not_already_exist(ISessionSource source)
    {
        if (IsNewDatabase) source.BuildSchema();
    }
 
    protected IDictionary<string, string> GetProperties()
    {
        MsSqlConfiguration config = MsSqlConfiguration.MsSql2005;
        config.ConnectionString.FromConnectionStringWithKey(“MYDBKEY”);
        config.ShowSql();
        config.UseOuterJoin();
 
        return config.ToProperties();
    }
    #endregion
}

A quick note here: We told SQLServerSessionSourceConfiguration to use a connection string from the app settings file (Web.Config) with a key of “MYDBKEY” This will be important later.

IUnitOfWork

public interface IUnitOfWork : IDisposable
{
    void Initialize();
    void Commit();
    void Rollback();
}

INHibernateUnitOfWork

public interface INHibernateUnitOfWork : IUnitOfWork
{
    ISession CurrentSession { get; }
}

NHibernateUnitOfWork

public class NHibernateUnitOfWork : INHibernateUnitOfWork
{
    private ITransaction _transaction;
    private bool _isDisposed;
    private readonly ISessionSource _source;
    private bool _isInitialized;
 
    public NHibernateUnitOfWork(ISessionSource source)
    {
        _source = source;
    }
 
    public void Initialize()
    {
        should_not_currently_be_disposed();
 
        CurrentSession = _source.CreateSession();
        begin_new_transaction();
 
        _isInitialized = true;
    }
 
    public ISession CurrentSession { get; private set; }
 
    public void Commit()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Commit();
 
        begin_new_transaction();
    }
 
    private void begin_new_transaction()
    {
        if (_transaction != null)
        {
            _transaction.Dispose();
        }
 
        _transaction = CurrentSession.BeginTransaction();
    }
 
    public void Rollback()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Rollback();
 
        begin_new_transaction();
    }
 
    private void should_not_currently_be_disposed()
    {
        if (_isDisposed) throw new ObjectDisposedException(GetType().Name);
    }
 
    private void should_be_initialized_first()
    {
        if (!_isInitialized) throw new InvalidOperationException("Must initialize (call Initialize()) on NHibernateUnitOfWork before commiting or rolling back");
    }
 
    public void Dispose()
    {
        if (_isDisposed || !_isInitialized) return;
 
        _transaction.Dispose();
        CurrentSession.Dispose();
 
        _isDisposed = true;
    }
}

IRepository

public interface IRepository
{
    void Save<ENTITY>(ENTITY entity)
        where ENTITY : DomainEntity;
 
    ENTITY Load<ENTITY>(Guid id)
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>()
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery)
        where ENTITY : DomainEntity;
 
    void Delete<ENTITY>(ENTITY entity);
 
    void DeleteAll<ENTITY>();
}

NHibernateRepository

public class NHibernateRepository : IRepository
{
    private readonly INHibernateUnitOfWork _unitOfWork;
 
    public NHibernateRepository(INHibernateUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public void Save<ENTITY>(ENTITY entity) where ENTITY : DomainEntity
    {
        _unitOfWork.CurrentSession.SaveOrUpdate(entity);
    }
 
    public ENTITY Load<ENTITY>(Guid id) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Load<ENTITY>(id);
    }
 
    public IQueryable<ENTITY> Query<ENTITY>() where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>();
    }
 
    public IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>().Where(whereQuery.Expression);
    }
 
    public void Delete<ENTITY>(ENTITY entity)
    {
        _unitOfWork.CurrentSession.Delete(entity);   
    }
 
    public void DeleteAll<ENTITY>()
    {
        var query = String.Format("from {0}", typeof(ENTITY).Name);
        _unitOfWork.CurrentSession.Delete(query);   
    }
}

DomainEntity

Note: I put both of these classes in my Core.Domain namespace, also XML comments are in Source Repository

public class DomainEntity : IEquatable<DomainEntity>
{
    public virtual Guid ID { get; set; }
 
    public virtual bool Equals(DomainEntity other)
    {
        if (ReferenceEquals(null, other)) return false;
        if (ReferenceEquals(this, other)) return true;
        return other.ID.Equals(ID);
    }
 
    public override bool Equals(object obj)
    {
        if (ReferenceEquals(null, obj)) return false;
        if (ReferenceEquals(this, obj)) return true;
        if (obj.GetType() != GetType()) return false;
        return Equals((DomainEntity)obj);
    }
 
    public override int GetHashCode()
    {
        return ID.GetHashCode();
    }
 
    public static bool operator ==(DomainEntity left, DomainEntity right)
    {
        return Equals(left, right);
    }
 
    public static bool operator !=(DomainEntity left, DomainEntity right)
    {
        return !Equals(left, right);
    }
}

IDomainQuery

public interface IDomainQuery<ENTITY>
    where ENTITY : DomainEntity
{
    Expression<Func<ENTITY, bool>> Expression { get; }
}

FubuSamplePersistenceModel

namespace FubuSample.Core.Domain.Persistence
{
    public class FubuSamplePersistenceModel : PersistenceModel
    {
        public FubuSamplePersistenceModel()
        {
            addMappingsFromThisAssembly();
        }
    }
}

Now that we have all the puzzle pieces in place we need to hook them up and make them do some work. Open up FubuSampleWebRegistry

And add the following code:

protected override void configure()
{
    ForRequestedType<ISessionSourceConfiguration>().AsSingletons()
        .TheDefault.Is.OfConcreteType<SQLServerSessionSourceConfiguration>();
 
 
    ForRequestedType<ISessionSource>().AsSingletons()
        .TheDefault.Is.ConstructedBy(ctx =>
                                     ctx.GetInstance<ISessionSourceConfiguration>()
                                         .CreateSessionSource(new FubuSamplePersistenceModel()));
 
    ForRequestedType<IUnitOfWork>().TheDefault.Is.ConstructedBy(ctx => ctx.GetInstance<INHibernateUnitOfWork>());
 
    ForRequestedType<INHibernateUnitOfWork>().CacheBy(InstanceScope.Hybrid)
        .TheDefault.Is.OfConcreteType<NHibernateUnitOfWork>();
 
    ForRequestedType<IRepository>().TheDefault.Is.OfConcreteType<NHibernateRepository>();
}

With a little luck and all of our mad skills, we should be able to talk to the database now. So we need to plumb our simple product object up to talk to NHibernate. We will do this with a mapping file, and since we are using FluentNHibernate we can do this strongly typed.

Make the following modifications to Product: Extend DomainEntity and get rid of Id Property, it is inherited

public class Product : DomainEntity
{
    public virtual string Name { get; set; }
    public virtual string Description { get; set; }
}

Add mapping file for Product:

namespace FubuSample.Core.Domain.Mapping
{
    public class ProductMap : ClassMap<Product>
    {
        public ProductMap()
        {
            Id(e => e.ID).GeneratedBy.GuidComb();
 
            Map(p => p.Name);
            Map(p => p.Description);
            
        }
    }
}

You may also want to setup your connection string at this point in the Web.Config file, mine looks like this:

<add name="MYDBKEY" connectionString="Data Source=LOCALHOST;initial catalog=FubuSample;Integrated Security=SSPI;" providerName="System.Data.SqlClient" />

I also created an empty database in my local SQL Server instance called “FubuSample” And then I went back to SQLServerSessionSourceConfiguration and changed the value of IsNewDatabase to return true. This will create the schema for the database when the application first runs. There is a multitude of different ways that we can handle this, but this was easy for the tutorial purposes.

Next we will add a behavior to our core project and tell FubuMVC to apply that behavior to all or our ControllerActions.

Create a class named “access_the_database_through_a_unit_of_work” in your Core.Web.Behaviors namespace. The contents will look like this:

public class access_the_database_through_a_unit_of_work : IControllerActionBehavior
{
    private readonly IUnitOfWork _unitOfWork;
 
    public access_the_database_through_a_unit_of_work(IUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public IControllerActionBehavior InsideBehavior { get; set; }
    public IInvocationResult Result { get; set; }
 
    public OUTPUT Invoke<INPUT, OUTPUT>(INPUT input, Func<INPUT, OUTPUT> func)
        where INPUT : class
        where OUTPUT : class
    {
        _unitOfWork.Initialize();
 
        try
        {
            var output = InsideBehavior.Invoke(input, func);
            Result = InsideBehavior.Result;
 
            _unitOfWork.Commit();
 
            return output;
        }
        catch
        {
            _unitOfWork.Rollback();
            throw;
        }
        finally
        {
            _unitOfWork.Dispose();
        }
    }
}

Now to tell FubuMVC what to do, open up Global.asax.cs or your Bootstrapper, wherever you are doing the configuration of FubuMVC. In this project we are doing it in Global.asax.cs Add a new behavior to the section that starts with “x.ByDefault.EveryControllerAction” so it looks like this:

x.ByDefault.EveryControllerAction(d =>
   {
       d.Will<execute_the_result>();
       d.Will<access_the_database_through_a_unit_of_work>();
   });

The last thing we will do is open up HomeController and add this code above the Index action:

private IRepository _repository;
 
public HomeController(IRepository repository)
{
    _repository = repository;
}

I also modified the Index action to go ahead and create some database values before we query for them just so we can test this thing. (I only did this for the tutorial, I swear) So modify the Index action to look like this:

public IndexViewModel Index(IndexSetupViewModel inModel)
{
    var prod1 = new Product {Name = "TestProduct1", Description = "This is a test product"};
 
    _repository.Save(prod1);
 
    var prod2 = new Product {Name = "TestProduct2", Description = "This is a test product"};
 
    _repository.Save(prod2);
 
    var outModel = new IndexViewModel();
 
    var productList = _repository.Query<Product>();
 
    outModel.Products = productList.ToList().Select(x => new ProductDisplay(x));
 
    return outModel;
}

Now with you should be able to run your web app and browse to /home and all this will be executed and you will be on your way to creating a whole bunch of persist able objects for use with your FubuMVC app.

As always, feedback is welcome.

]]> http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/feed/ 9 It’s Official – New Gig started last week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/?utm_source=rss&utm_medium=rss&utm_campaign=its-official-new-gig-started-last-week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/#comments Tue, 24 Feb 2009 19:03:21 +0000 Ryan Kelley http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/ CoachesAid.com. CoachesAid is a High School sports website that is expanding rapidly and it is my task to make this expansion happen as smoothly and as quickly as possible. The past month has been very hectic as I was wrapping up loose ends at my previous engagement. I started my new gig last week, but I have pretty much been building furniture and getting computer and server ready to go. The next few weeks will also be challenging as I start to assemble the team of people that is going to make this all happen. How does this tie into the practice of Elegant Coding? Funny you should ask that, the current infrastructure they are built on is a maintenance nightmare so project number one is to completely redo their entire site infrastructure in ASP.Net, and yes it will be MVC based, but not ASP.Net MVC. I am going to architect and build their new infrastructure from the ground up on FubuMVC. So expect a lot more posts from me on FubuMVC and I may even have questions for you dear reader. Side Note: I just finished deploying to production a small scale site built on FubuMVC, and it ROCKS! There is going to be some stuff that needs to be tweaked out and added to the core, but overall, fully functional MVC framework. I hope I haven’t bored you with too much personal information, but I have to go. (I have several FubuMVC posts stacked up in my queue) -Ryan]]> http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/feed/ 8 Quick 2008 Recap and a few New Years Resolutions http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/?utm_source=rss&utm_medium=rss&utm_campaign=quick-2008-recap-and-a-few-new-years-resolutions http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/#comments Thu, 01 Jan 2009 15:57:06 +0000 Ryan Kelley http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/ Whew, I cannot believe that 2008 is over already, it seems like it just started. 2008 was a great year for me as a developer for several reasons.

Met new People

I was able to meet a ton of new people in 2008, both online through blogs and other communities, and at KaizenConf in Austin. This is probably the single most important thing that happened to me in 2008 because it helped put me into circle of people that share the same thoughts and values about software development that I do.

Alt.Net Introduction

I was also introduced to the Alt.Net movement during 2008. I have been developing software for several years and some of the things I had been doing just didn’t seem quite right, they worked, but they had a smell to them. Enter Alt.Net, this stuff just makes sense. It is smart software development, that revolves around creating highly testable, highly maintainable code that follows the SOLID design principles. I have come to realize that if you just ask yourself “How does this proposed solution adhere to the SOLID principles” you will write much more elegant code.

KaizenConf Open Spaces Conference

This was my first open spaces conference and I didn’t know what to expect but I came away with the feeling that this was the best conference I had ever been to. KaizenConf helped fuel my fire for continuing with more Alt.Net stuff, working on Lean Software Development and KanBan methods, and staying involved with the community. It even spurred me to start blogging more frequently about these topics.

Some 2009 Resolutions

I have a few resolutions I am going to make for the new year, some are computer related, some are not.

  • Blog More – I am targeting 52 blog posts in 2009, that is a little more than double from 2008 and is only 1 per week.
  • Fish more, I love fly fishing, just need to make more time
    • Fly Fish for Bass – talk about fun!
  • Write Elegant Code – I am staying committed to SOLID principles, testability and maintainable code.
  • Learn more about Asp.Net – Especially MVC stuff, I have been doing WinForms development for the past 4 years, so I am looking forward to this one.
  • Learn a new Programming Language – Everybody should do this every year.

I am going to stop there, I don’t want to set any unrealistic expectations for myself during the year. I think all of these are very attainable and I hope that my list has spurred some inner resolution making within you to go out and commit to something new in 2009.

]]> http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/feed/ 2 Hello Elegant Code Readers http://elegantcode.com/2008/12/02/hello-elegant-code-readers/?utm_source=rss&utm_medium=rss&utm_campaign=hello-elegant-code-readers http://elegantcode.com/2008/12/02/hello-elegant-code-readers/#comments Tue, 02 Dec 2008 15:18:27 +0000 Ryan Kelley http://elegantcode.com/2008/12/02/hello-elegant-code-readers/ As Jarod Ferguson already mentioned, I am now part of the Elegant Code team. I must say it is an honor to be invited to join this community and I am very excited about this opportunity. I will still cross-post on my own blog as well as here on elegantcode.com.

I am a pretty easy going guy, so hopefully this opportunity will spur me into posting with more regularity. If anybody has any topics they want me to write about just drop me a line.

One last thing, Thank You to all the Elegant Coders for giving me the invite.

]]> http://elegantcode.com/2008/12/02/hello-elegant-code-readers/feed/ 3 Joining Elegant Code http://elegantcode.com/2008/11/22/joining-elegant-code/?utm_source=rss&utm_medium=rss&utm_campaign=joining-elegant-code http://elegantcode.com/2008/11/22/joining-elegant-code/#comments Sun, 23 Nov 2008 00:52:53 +0000 Guest Blogger http://elegantcode.com/?p=1545 mentioned, i am now part of the Elegant Code team. It's an honor to be invited and i'm obviously very happy with this. All of my posts will still be posted to my own blog, as well as on elegantcode.com. And the NHibernate posts will also continue to be cross posted to NHForge. Now if you'll excuse me, i've got to start writing some posts ;)]]> http://elegantcode.com/2008/11/22/joining-elegant-code/feed/ 2 The New Blogger Toolkit http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/?utm_source=rss&utm_medium=rss&utm_campaign=welcome-two-new-elegant-coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/#comments Thu, 15 Oct 2009 19:58:17 +0000 David Starr http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/ I am happy to introduce 2 new Elegant Coders! We are excited to have their contributions to the site and look forward to their wisdom.

Kirstin Juhl

@kirstinj

We are excited to have Kirstin drop wisdom like she has been doing on her current blog: I [heart] Code. From her own bio:

I am a former engineer who writes code. I did Toyota Operating System, Kanban, and Lean in my factories a decade ago, and am fascinated by its use in software development today. You can take the girl out of the factory, but you cannot take the engineer out of the girl, and so I approach everything in life as a problem to solved or optimized. Including software development. I strive to be a craftsman.

I am a mom, and I take lessons from parenthood into my work everyday.

Jason Jarrett

@staxmanade

Jason is a big-time Silverlight maven and the developer behind StatLight, a set of unit testing tools for Silverlight. I knew he was perfect for the tribe when he said, “… and so I added automocking to Unity for Silverlight.”

Yeah. :)

Welcome all.

]]> http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/feed/ 0 Elegant Code » Blogging http://elegantcode.com Tue, 15 May 2012 10:00:00 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 I guess an introduction is in order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/?utm_source=rss&utm_medium=rss&utm_campaign=i-guess-an-introduction-is-in-order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/#comments Sun, 15 Aug 2010 21:50:26 +0000 Andreas Håkansson http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/ Twitter or from my self-titled blog that I have been blogging on up until this point (and might continue doing, haven’t really made up my mind yet what I am going to do with it). However, my real name is Andreas Håkansson and I guess I could describe myself as a nearly 30 year old .NET developer from Sweden, with a passion for pretty much everything in the software engineering / craftsmanship department (hey, why limit yourself to one kind of cake when there’s so much to be had out there!). I am a strong advocator of Open-Source Software and I head the MEF Contrib project, a set of community contributed extensions, tools and samples for the Managed Extensibility Framework, and I have also created the Common Service Factory, a WCF extension that enabled dependency injection in services (it’s a bit dated, but it works like a charm – probably should give it some love as soon as I can find a slice of spare time in my life). Oh yeah, there’s more to me than being a code ninjah – somehow I’ve also managed to get married to my high school sweetheart (12 years since we hooked up and still going strong) and together we have two wonderful boys (3 and 1½ years old – boy do they know how to keep us busy hehe) Well I guess that’s it… now you know a bit about me, and I hope to get to know a bit more about you, the readers of Elegant Code, so please stop by my posts and drop me a line or two. See you there!]]> http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/feed/ 2 What Does Elegant Code Mean to Me? http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/?utm_source=rss&utm_medium=rss&utm_campaign=what-does-elegant-code-mean-to-me http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/#comments Fri, 09 Apr 2010 19:46:38 +0000 John Sonmez http://elegantcode.com/?p=3434 What is elegance? Simply stated. Something that is simple yet effective, delivered with grace. Being simple is not enough. Simple lacking effectiveness is just a waste of time. Simple - Not Effective Simple, but not effective is a foam hammer. You don't want your code to be like a foam hammer. If it can't do what it supposed to do the simplicity just looks like stupidity instead. Effective, but not simple is something that gets thrown away or lamented. It's a Rube Goldberg machine. Rube Goldberg Machine You don't want your code to be like a Rube Goldberg machine either.  Where people look at your code because it is such a spectacle.  You don't want someone to look at your code and immediately think they want to kill you.  Code that evokes murderous rage, tends to get blamed for anything that goes wrong in the system, even if it works perfectly. If you can build something simple and its effective, it still has to be delivered in a graceful way. Consider, the elephant harness... Simple and Effective - Not Graceful Simple?  Yes, it's a box strapped on top of an Elephant, can't get much more simple than that.  Effective?  Yes, looks to me like that elephant will get you where you need to go in that terrain.  Delivered with grace?  Hmm...  Do you want to ride around on an elephant? Even if you nail the first two, with your code, you should make sure it looks and reads good.  No one wants to ride an elephant.  I have seen more than one simple effective design get thrown away because the variables were named things like "cntr" and "banana".

Elegant Code is James Bond

Women love him, men want to be like him and he kills people with a simple sophistication. When people read your code they should think James Bond, not Booger from Revenge of the Nerds. James-Bond Vs. booger
Elegant code to me is code that reads well, does what is is supposed to do and is easy to maintain. Now that I have told you what I think elegant code is, in future posts I will talk more about how to actually write elegant code.

Side Note - Joining Elegant Code

First of all I wanted to publicly thank the other Elegant Coders for inviting me to join their community. I feel honored and esteemed to be joining such a great group of software craftsmen. I also wanted to clear up confusion for anyone who has been following my blog at http://simpleprogrammer.com.  I will still be blogging there, so don't change your RSS feeds, but in addition I will be blogging here at ElegantCode.com.  If you've come here form a link on my personal blog, I encourage you to check out the other excellent bloggers on this site and consider adding Elegant Code to your RSS feed reader.   My personal blog will contain a wider array of topics, but my content here at ElegantCode.com will be centered around the theme of writing elegant code. As always, feel free to email me at john *dot* sonmez *at* gmail.com or follow me on twitter.]]> http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/feed/ 1 Welcome Two New Elegant Coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/?utm_source=rss&utm_medium=rss&utm_campaign=welcome-two-new-elegant-coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/#comments Thu, 15 Oct 2009 19:58:17 +0000 David Starr http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/ I am happy to introduce 2 new Elegant Coders! We are excited to have their contributions to the site and look forward to their wisdom.

Kirstin Juhl

@kirstinj

We are excited to have Kirstin drop wisdom like she has been doing on her current blog: I [heart] Code. From her own bio:

I am a former engineer who writes code. I did Toyota Operating System, Kanban, and Lean in my factories a decade ago, and am fascinated by its use in software development today. You can take the girl out of the factory, but you cannot take the engineer out of the girl, and so I approach everything in life as a problem to solved or optimized. Including software development. I strive to be a craftsman.

I am a mom, and I take lessons from parenthood into my work everyday.

Jason Jarrett

@staxmanade

Jason is a big-time Silverlight maven and the developer behind StatLight, a set of unit testing tools for Silverlight. I knew he was perfect for the tribe when he said, “… and so I added automocking to Unity for Silverlight.”

Yeah. :)

Welcome all.

]]> http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/feed/ 0 FubuMVC From Scratch – Part 4 Persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/?utm_source=rss&utm_medium=rss&utm_campaign=fubumvc-from-scratch-part-4-persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/#comments Wed, 25 Mar 2009 21:22:00 +0000 Ryan Kelley http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/ Previous posts in series:

Persistence is a requirement in virtually every application that we write today, and now the time has come for us to add a persistence model to our FubuMVC app. I know I mentioned moving my samples to the FubuCart source, but I am going to go ahead and implement the persistence piece in the same project the previous articles using, FubuSample. I have also added all the code for this series to the FubuMVC-Contrib project

We will be implementing our persistence model to use NHibernate, Fluent NHibernate, Repository Pattern and UnitOfWork pattern all on top of SQL Express or standard. This will also work for sqllite and other database servers.

Class and Interfaces we have to implement:

  • ISessionSourceConfiguration
  • SQLServerSessionSourceConfiguration
  • IUnitOfWork
  • INHibernateUnitOfWork
  • NHibernateUnitOfWork
  • IRepository
  • NHibernateRepository
  • DomainEntity
  • IDomainQuery
  • FubuSamplePersistenceModel

Note: I put the first two in the list in my Core.Config namespace, and the rest in Core.Persistence

Before we start you probably want to go ahead and add the following references to your core project and Web project

FubuMVC-Persist-Ref

Let’s just work our way down the list and get these files implemented.

ISessionSourceConfiguration

public interface ISessionSourceConfiguration
{
    bool IsNewDatabase { get; }
    ISessionSource CreateSessionSource(PersistenceModel model);
}

SQLServerSessionSourceConfiguration

public class SQLServerSessionSourceConfiguration : ISessionSourceConfiguration
{
    #region Implementation of ISessionSourceConfiguration
 
    public bool IsNewDatabase
    {
        get { return false; }
    }
 
    public ISessionSource CreateSessionSource(PersistenceModel model)
    {
        var properties = GetProperties();
        var source = new SessionSource(properties, model);
 
        create_schema_if_it_does_not_already_exist(source);
 
        return source;
    }
 
    private void create_schema_if_it_does_not_already_exist(ISessionSource source)
    {
        if (IsNewDatabase) source.BuildSchema();
    }
 
    protected IDictionary<string, string> GetProperties()
    {
        MsSqlConfiguration config = MsSqlConfiguration.MsSql2005;
        config.ConnectionString.FromConnectionStringWithKey(“MYDBKEY”);
        config.ShowSql();
        config.UseOuterJoin();
 
        return config.ToProperties();
    }
    #endregion
}

A quick note here: We told SQLServerSessionSourceConfiguration to use a connection string from the app settings file (Web.Config) with a key of “MYDBKEY” This will be important later.

IUnitOfWork

public interface IUnitOfWork : IDisposable
{
    void Initialize();
    void Commit();
    void Rollback();
}

INHibernateUnitOfWork

public interface INHibernateUnitOfWork : IUnitOfWork
{
    ISession CurrentSession { get; }
}

NHibernateUnitOfWork

public class NHibernateUnitOfWork : INHibernateUnitOfWork
{
    private ITransaction _transaction;
    private bool _isDisposed;
    private readonly ISessionSource _source;
    private bool _isInitialized;
 
    public NHibernateUnitOfWork(ISessionSource source)
    {
        _source = source;
    }
 
    public void Initialize()
    {
        should_not_currently_be_disposed();
 
        CurrentSession = _source.CreateSession();
        begin_new_transaction();
 
        _isInitialized = true;
    }
 
    public ISession CurrentSession { get; private set; }
 
    public void Commit()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Commit();
 
        begin_new_transaction();
    }
 
    private void begin_new_transaction()
    {
        if (_transaction != null)
        {
            _transaction.Dispose();
        }
 
        _transaction = CurrentSession.BeginTransaction();
    }
 
    public void Rollback()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Rollback();
 
        begin_new_transaction();
    }
 
    private void should_not_currently_be_disposed()
    {
        if (_isDisposed) throw new ObjectDisposedException(GetType().Name);
    }
 
    private void should_be_initialized_first()
    {
        if (!_isInitialized) throw new InvalidOperationException("Must initialize (call Initialize()) on NHibernateUnitOfWork before commiting or rolling back");
    }
 
    public void Dispose()
    {
        if (_isDisposed || !_isInitialized) return;
 
        _transaction.Dispose();
        CurrentSession.Dispose();
 
        _isDisposed = true;
    }
}

IRepository

public interface IRepository
{
    void Save<ENTITY>(ENTITY entity)
        where ENTITY : DomainEntity;
 
    ENTITY Load<ENTITY>(Guid id)
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>()
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery)
        where ENTITY : DomainEntity;
 
    void Delete<ENTITY>(ENTITY entity);
 
    void DeleteAll<ENTITY>();
}

NHibernateRepository

public class NHibernateRepository : IRepository
{
    private readonly INHibernateUnitOfWork _unitOfWork;
 
    public NHibernateRepository(INHibernateUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public void Save<ENTITY>(ENTITY entity) where ENTITY : DomainEntity
    {
        _unitOfWork.CurrentSession.SaveOrUpdate(entity);
    }
 
    public ENTITY Load<ENTITY>(Guid id) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Load<ENTITY>(id);
    }
 
    public IQueryable<ENTITY> Query<ENTITY>() where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>();
    }
 
    public IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>().Where(whereQuery.Expression);
    }
 
    public void Delete<ENTITY>(ENTITY entity)
    {
        _unitOfWork.CurrentSession.Delete(entity);   
    }
 
    public void DeleteAll<ENTITY>()
    {
        var query = String.Format("from {0}", typeof(ENTITY).Name);
        _unitOfWork.CurrentSession.Delete(query);   
    }
}

DomainEntity

Note: I put both of these classes in my Core.Domain namespace, also XML comments are in Source Repository

public class DomainEntity : IEquatable<DomainEntity>
{
    public virtual Guid ID { get; set; }
 
    public virtual bool Equals(DomainEntity other)
    {
        if (ReferenceEquals(null, other)) return false;
        if (ReferenceEquals(this, other)) return true;
        return other.ID.Equals(ID);
    }
 
    public override bool Equals(object obj)
    {
        if (ReferenceEquals(null, obj)) return false;
        if (ReferenceEquals(this, obj)) return true;
        if (obj.GetType() != GetType()) return false;
        return Equals((DomainEntity)obj);
    }
 
    public override int GetHashCode()
    {
        return ID.GetHashCode();
    }
 
    public static bool operator ==(DomainEntity left, DomainEntity right)
    {
        return Equals(left, right);
    }
 
    public static bool operator !=(DomainEntity left, DomainEntity right)
    {
        return !Equals(left, right);
    }
}

IDomainQuery

public interface IDomainQuery<ENTITY>
    where ENTITY : DomainEntity
{
    Expression<Func<ENTITY, bool>> Expression { get; }
}

FubuSamplePersistenceModel

namespace FubuSample.Core.Domain.Persistence
{
    public class FubuSamplePersistenceModel : PersistenceModel
    {
        public FubuSamplePersistenceModel()
        {
            addMappingsFromThisAssembly();
        }
    }
}

Now that we have all the puzzle pieces in place we need to hook them up and make them do some work. Open up FubuSampleWebRegistry

And add the following code:

protected override void configure()
{
    ForRequestedType<ISessionSourceConfiguration>().AsSingletons()
        .TheDefault.Is.OfConcreteType<SQLServerSessionSourceConfiguration>();
 
 
    ForRequestedType<ISessionSource>().AsSingletons()
        .TheDefault.Is.ConstructedBy(ctx =>
                                     ctx.GetInstance<ISessionSourceConfiguration>()
                                         .CreateSessionSource(new FubuSamplePersistenceModel()));
 
    ForRequestedType<IUnitOfWork>().TheDefault.Is.ConstructedBy(ctx => ctx.GetInstance<INHibernateUnitOfWork>());
 
    ForRequestedType<INHibernateUnitOfWork>().CacheBy(InstanceScope.Hybrid)
        .TheDefault.Is.OfConcreteType<NHibernateUnitOfWork>();
 
    ForRequestedType<IRepository>().TheDefault.Is.OfConcreteType<NHibernateRepository>();
}

With a little luck and all of our mad skills, we should be able to talk to the database now. So we need to plumb our simple product object up to talk to NHibernate. We will do this with a mapping file, and since we are using FluentNHibernate we can do this strongly typed.

Make the following modifications to Product: Extend DomainEntity and get rid of Id Property, it is inherited

public class Product : DomainEntity
{
    public virtual string Name { get; set; }
    public virtual string Description { get; set; }
}

Add mapping file for Product:

namespace FubuSample.Core.Domain.Mapping
{
    public class ProductMap : ClassMap<Product>
    {
        public ProductMap()
        {
            Id(e => e.ID).GeneratedBy.GuidComb();
 
            Map(p => p.Name);
            Map(p => p.Description);
            
        }
    }
}

You may also want to setup your connection string at this point in the Web.Config file, mine looks like this:

<add name="MYDBKEY" connectionString="Data Source=LOCALHOST;initial catalog=FubuSample;Integrated Security=SSPI;" providerName="System.Data.SqlClient" />

I also created an empty database in my local SQL Server instance called “FubuSample” And then I went back to SQLServerSessionSourceConfiguration and changed the value of IsNewDatabase to return true. This will create the schema for the database when the application first runs. There is a multitude of different ways that we can handle this, but this was easy for the tutorial purposes.

Next we will add a behavior to our core project and tell FubuMVC to apply that behavior to all or our ControllerActions.

Create a class named “access_the_database_through_a_unit_of_work” in your Core.Web.Behaviors namespace. The contents will look like this:

public class access_the_database_through_a_unit_of_work : IControllerActionBehavior
{
    private readonly IUnitOfWork _unitOfWork;
 
    public access_the_database_through_a_unit_of_work(IUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public IControllerActionBehavior InsideBehavior { get; set; }
    public IInvocationResult Result { get; set; }
 
    public OUTPUT Invoke<INPUT, OUTPUT>(INPUT input, Func<INPUT, OUTPUT> func)
        where INPUT : class
        where OUTPUT : class
    {
        _unitOfWork.Initialize();
 
        try
        {
            var output = InsideBehavior.Invoke(input, func);
            Result = InsideBehavior.Result;
 
            _unitOfWork.Commit();
 
            return output;
        }
        catch
        {
            _unitOfWork.Rollback();
            throw;
        }
        finally
        {
            _unitOfWork.Dispose();
        }
    }
}

Now to tell FubuMVC what to do, open up Global.asax.cs or your Bootstrapper, wherever you are doing the configuration of FubuMVC. In this project we are doing it in Global.asax.cs Add a new behavior to the section that starts with “x.ByDefault.EveryControllerAction” so it looks like this:

x.ByDefault.EveryControllerAction(d =>
   {
       d.Will<execute_the_result>();
       d.Will<access_the_database_through_a_unit_of_work>();
   });

The last thing we will do is open up HomeController and add this code above the Index action:

private IRepository _repository;
 
public HomeController(IRepository repository)
{
    _repository = repository;
}

I also modified the Index action to go ahead and create some database values before we query for them just so we can test this thing. (I only did this for the tutorial, I swear) So modify the Index action to look like this:

public IndexViewModel Index(IndexSetupViewModel inModel)
{
    var prod1 = new Product {Name = "TestProduct1", Description = "This is a test product"};
 
    _repository.Save(prod1);
 
    var prod2 = new Product {Name = "TestProduct2", Description = "This is a test product"};
 
    _repository.Save(prod2);
 
    var outModel = new IndexViewModel();
 
    var productList = _repository.Query<Product>();
 
    outModel.Products = productList.ToList().Select(x => new ProductDisplay(x));
 
    return outModel;
}

Now with you should be able to run your web app and browse to /home and all this will be executed and you will be on your way to creating a whole bunch of persist able objects for use with your FubuMVC app.

As always, feedback is welcome.

]]> http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/feed/ 9 It’s Official – New Gig started last week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/?utm_source=rss&utm_medium=rss&utm_campaign=its-official-new-gig-started-last-week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/#comments Tue, 24 Feb 2009 19:03:21 +0000 Ryan Kelley http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/ CoachesAid.com. CoachesAid is a High School sports website that is expanding rapidly and it is my task to make this expansion happen as smoothly and as quickly as possible. The past month has been very hectic as I was wrapping up loose ends at my previous engagement. I started my new gig last week, but I have pretty much been building furniture and getting computer and server ready to go. The next few weeks will also be challenging as I start to assemble the team of people that is going to make this all happen. How does this tie into the practice of Elegant Coding? Funny you should ask that, the current infrastructure they are built on is a maintenance nightmare so project number one is to completely redo their entire site infrastructure in ASP.Net, and yes it will be MVC based, but not ASP.Net MVC. I am going to architect and build their new infrastructure from the ground up on FubuMVC. So expect a lot more posts from me on FubuMVC and I may even have questions for you dear reader. Side Note: I just finished deploying to production a small scale site built on FubuMVC, and it ROCKS! There is going to be some stuff that needs to be tweaked out and added to the core, but overall, fully functional MVC framework. I hope I haven’t bored you with too much personal information, but I have to go. (I have several FubuMVC posts stacked up in my queue) -Ryan]]> http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/feed/ 8 Quick 2008 Recap and a few New Years Resolutions http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/?utm_source=rss&utm_medium=rss&utm_campaign=quick-2008-recap-and-a-few-new-years-resolutions http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/#comments Thu, 01 Jan 2009 15:57:06 +0000 Ryan Kelley http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/ Whew, I cannot believe that 2008 is over already, it seems like it just started. 2008 was a great year for me as a developer for several reasons.

Met new People

I was able to meet a ton of new people in 2008, both online through blogs and other communities, and at KaizenConf in Austin. This is probably the single most important thing that happened to me in 2008 because it helped put me into circle of people that share the same thoughts and values about software development that I do.

Alt.Net Introduction

I was also introduced to the Alt.Net movement during 2008. I have been developing software for several years and some of the things I had been doing just didn’t seem quite right, they worked, but they had a smell to them. Enter Alt.Net, this stuff just makes sense. It is smart software development, that revolves around creating highly testable, highly maintainable code that follows the SOLID design principles. I have come to realize that if you just ask yourself “How does this proposed solution adhere to the SOLID principles” you will write much more elegant code.

KaizenConf Open Spaces Conference

This was my first open spaces conference and I didn’t know what to expect but I came away with the feeling that this was the best conference I had ever been to. KaizenConf helped fuel my fire for continuing with more Alt.Net stuff, working on Lean Software Development and KanBan methods, and staying involved with the community. It even spurred me to start blogging more frequently about these topics.

Some 2009 Resolutions

I have a few resolutions I am going to make for the new year, some are computer related, some are not.

  • Blog More – I am targeting 52 blog posts in 2009, that is a little more than double from 2008 and is only 1 per week.
  • Fish more, I love fly fishing, just need to make more time
    • Fly Fish for Bass – talk about fun!
  • Write Elegant Code – I am staying committed to SOLID principles, testability and maintainable code.
  • Learn more about Asp.Net – Especially MVC stuff, I have been doing WinForms development for the past 4 years, so I am looking forward to this one.
  • Learn a new Programming Language – Everybody should do this every year.

I am going to stop there, I don’t want to set any unrealistic expectations for myself during the year. I think all of these are very attainable and I hope that my list has spurred some inner resolution making within you to go out and commit to something new in 2009.

]]> http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/feed/ 2 Hello Elegant Code Readers http://elegantcode.com/2008/12/02/hello-elegant-code-readers/?utm_source=rss&utm_medium=rss&utm_campaign=hello-elegant-code-readers http://elegantcode.com/2008/12/02/hello-elegant-code-readers/#comments Tue, 02 Dec 2008 15:18:27 +0000 Ryan Kelley http://elegantcode.com/2008/12/02/hello-elegant-code-readers/ As Jarod Ferguson already mentioned, I am now part of the Elegant Code team. I must say it is an honor to be invited to join this community and I am very excited about this opportunity. I will still cross-post on my own blog as well as here on elegantcode.com.

I am a pretty easy going guy, so hopefully this opportunity will spur me into posting with more regularity. If anybody has any topics they want me to write about just drop me a line.

One last thing, Thank You to all the Elegant Coders for giving me the invite.

]]> http://elegantcode.com/2008/12/02/hello-elegant-code-readers/feed/ 3 Joining Elegant Code http://elegantcode.com/2008/11/22/joining-elegant-code/?utm_source=rss&utm_medium=rss&utm_campaign=joining-elegant-code http://elegantcode.com/2008/11/22/joining-elegant-code/#comments Sun, 23 Nov 2008 00:52:53 +0000 Guest Blogger http://elegantcode.com/?p=1545 mentioned, i am now part of the Elegant Code team. It's an honor to be invited and i'm obviously very happy with this. All of my posts will still be posted to my own blog, as well as on elegantcode.com. And the NHibernate posts will also continue to be cross posted to NHForge. Now if you'll excuse me, i've got to start writing some posts ;)]]> http://elegantcode.com/2008/11/22/joining-elegant-code/feed/ 2 The New Blogger Toolkit http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/?utm_source=rss&utm_medium=rss&utm_campaign=fubumvc-from-scratch-part-4-persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/#comments Wed, 25 Mar 2009 21:22:00 +0000 Ryan Kelley http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/ Previous posts in series:

Persistence is a requirement in virtually every application that we write today, and now the time has come for us to add a persistence model to our FubuMVC app. I know I mentioned moving my samples to the FubuCart source, but I am going to go ahead and implement the persistence piece in the same project the previous articles using, FubuSample. I have also added all the code for this series to the FubuMVC-Contrib project

We will be implementing our persistence model to use NHibernate, Fluent NHibernate, Repository Pattern and UnitOfWork pattern all on top of SQL Express or standard. This will also work for sqllite and other database servers.

Class and Interfaces we have to implement:

  • ISessionSourceConfiguration
  • SQLServerSessionSourceConfiguration
  • IUnitOfWork
  • INHibernateUnitOfWork
  • NHibernateUnitOfWork
  • IRepository
  • NHibernateRepository
  • DomainEntity
  • IDomainQuery
  • FubuSamplePersistenceModel

Note: I put the first two in the list in my Core.Config namespace, and the rest in Core.Persistence

Before we start you probably want to go ahead and add the following references to your core project and Web project

FubuMVC-Persist-Ref

Let’s just work our way down the list and get these files implemented.

ISessionSourceConfiguration

public interface ISessionSourceConfiguration
{
    bool IsNewDatabase { get; }
    ISessionSource CreateSessionSource(PersistenceModel model);
}

SQLServerSessionSourceConfiguration

public class SQLServerSessionSourceConfiguration : ISessionSourceConfiguration
{
    #region Implementation of ISessionSourceConfiguration
 
    public bool IsNewDatabase
    {
        get { return false; }
    }
 
    public ISessionSource CreateSessionSource(PersistenceModel model)
    {
        var properties = GetProperties();
        var source = new SessionSource(properties, model);
 
        create_schema_if_it_does_not_already_exist(source);
 
        return source;
    }
 
    private void create_schema_if_it_does_not_already_exist(ISessionSource source)
    {
        if (IsNewDatabase) source.BuildSchema();
    }
 
    protected IDictionary<string, string> GetProperties()
    {
        MsSqlConfiguration config = MsSqlConfiguration.MsSql2005;
        config.ConnectionString.FromConnectionStringWithKey(“MYDBKEY”);
        config.ShowSql();
        config.UseOuterJoin();
 
        return config.ToProperties();
    }
    #endregion
}

A quick note here: We told SQLServerSessionSourceConfiguration to use a connection string from the app settings file (Web.Config) with a key of “MYDBKEY” This will be important later.

IUnitOfWork

public interface IUnitOfWork : IDisposable
{
    void Initialize();
    void Commit();
    void Rollback();
}

INHibernateUnitOfWork

public interface INHibernateUnitOfWork : IUnitOfWork
{
    ISession CurrentSession { get; }
}

NHibernateUnitOfWork

public class NHibernateUnitOfWork : INHibernateUnitOfWork
{
    private ITransaction _transaction;
    private bool _isDisposed;
    private readonly ISessionSource _source;
    private bool _isInitialized;
 
    public NHibernateUnitOfWork(ISessionSource source)
    {
        _source = source;
    }
 
    public void Initialize()
    {
        should_not_currently_be_disposed();
 
        CurrentSession = _source.CreateSession();
        begin_new_transaction();
 
        _isInitialized = true;
    }
 
    public ISession CurrentSession { get; private set; }
 
    public void Commit()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Commit();
 
        begin_new_transaction();
    }
 
    private void begin_new_transaction()
    {
        if (_transaction != null)
        {
            _transaction.Dispose();
        }
 
        _transaction = CurrentSession.BeginTransaction();
    }
 
    public void Rollback()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Rollback();
 
        begin_new_transaction();
    }
 
    private void should_not_currently_be_disposed()
    {
        if (_isDisposed) throw new ObjectDisposedException(GetType().Name);
    }
 
    private void should_be_initialized_first()
    {
        if (!_isInitialized) throw new InvalidOperationException("Must initialize (call Initialize()) on NHibernateUnitOfWork before commiting or rolling back");
    }
 
    public void Dispose()
    {
        if (_isDisposed || !_isInitialized) return;
 
        _transaction.Dispose();
        CurrentSession.Dispose();
 
        _isDisposed = true;
    }
}

IRepository

public interface IRepository
{
    void Save<ENTITY>(ENTITY entity)
        where ENTITY : DomainEntity;
 
    ENTITY Load<ENTITY>(Guid id)
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>()
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery)
        where ENTITY : DomainEntity;
 
    void Delete<ENTITY>(ENTITY entity);
 
    void DeleteAll<ENTITY>();
}

NHibernateRepository

public class NHibernateRepository : IRepository
{
    private readonly INHibernateUnitOfWork _unitOfWork;
 
    public NHibernateRepository(INHibernateUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public void Save<ENTITY>(ENTITY entity) where ENTITY : DomainEntity
    {
        _unitOfWork.CurrentSession.SaveOrUpdate(entity);
    }
 
    public ENTITY Load<ENTITY>(Guid id) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Load<ENTITY>(id);
    }
 
    public IQueryable<ENTITY> Query<ENTITY>() where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>();
    }
 
    public IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>().Where(whereQuery.Expression);
    }
 
    public void Delete<ENTITY>(ENTITY entity)
    {
        _unitOfWork.CurrentSession.Delete(entity);   
    }
 
    public void DeleteAll<ENTITY>()
    {
        var query = String.Format("from {0}", typeof(ENTITY).Name);
        _unitOfWork.CurrentSession.Delete(query);   
    }
}

DomainEntity

Note: I put both of these classes in my Core.Domain namespace, also XML comments are in Source Repository

public class DomainEntity : IEquatable<DomainEntity>
{
    public virtual Guid ID { get; set; }
 
    public virtual bool Equals(DomainEntity other)
    {
        if (ReferenceEquals(null, other)) return false;
        if (ReferenceEquals(this, other)) return true;
        return other.ID.Equals(ID);
    }
 
    public override bool Equals(object obj)
    {
        if (ReferenceEquals(null, obj)) return false;
        if (ReferenceEquals(this, obj)) return true;
        if (obj.GetType() != GetType()) return false;
        return Equals((DomainEntity)obj);
    }
 
    public override int GetHashCode()
    {
        return ID.GetHashCode();
    }
 
    public static bool operator ==(DomainEntity left, DomainEntity right)
    {
        return Equals(left, right);
    }
 
    public static bool operator !=(DomainEntity left, DomainEntity right)
    {
        return !Equals(left, right);
    }
}

IDomainQuery

public interface IDomainQuery<ENTITY>
    where ENTITY : DomainEntity
{
    Expression<Func<ENTITY, bool>> Expression { get; }
}

FubuSamplePersistenceModel

namespace FubuSample.Core.Domain.Persistence
{
    public class FubuSamplePersistenceModel : PersistenceModel
    {
        public FubuSamplePersistenceModel()
        {
            addMappingsFromThisAssembly();
        }
    }
}

Now that we have all the puzzle pieces in place we need to hook them up and make them do some work. Open up FubuSampleWebRegistry

And add the following code:

protected override void configure()
{
    ForRequestedType<ISessionSourceConfiguration>().AsSingletons()
        .TheDefault.Is.OfConcreteType<SQLServerSessionSourceConfiguration>();
 
 
    ForRequestedType<ISessionSource>().AsSingletons()
        .TheDefault.Is.ConstructedBy(ctx =>
                                     ctx.GetInstance<ISessionSourceConfiguration>()
                                         .CreateSessionSource(new FubuSamplePersistenceModel()));
 
    ForRequestedType<IUnitOfWork>().TheDefault.Is.ConstructedBy(ctx => ctx.GetInstance<INHibernateUnitOfWork>());
 
    ForRequestedType<INHibernateUnitOfWork>().CacheBy(InstanceScope.Hybrid)
        .TheDefault.Is.OfConcreteType<NHibernateUnitOfWork>();
 
    ForRequestedType<IRepository>().TheDefault.Is.OfConcreteType<NHibernateRepository>();
}

With a little luck and all of our mad skills, we should be able to talk to the database now. So we need to plumb our simple product object up to talk to NHibernate. We will do this with a mapping file, and since we are using FluentNHibernate we can do this strongly typed.

Make the following modifications to Product: Extend DomainEntity and get rid of Id Property, it is inherited

public class Product : DomainEntity
{
    public virtual string Name { get; set; }
    public virtual string Description { get; set; }
}

Add mapping file for Product:

namespace FubuSample.Core.Domain.Mapping
{
    public class ProductMap : ClassMap<Product>
    {
        public ProductMap()
        {
            Id(e => e.ID).GeneratedBy.GuidComb();
 
            Map(p => p.Name);
            Map(p => p.Description);
            
        }
    }
}

You may also want to setup your connection string at this point in the Web.Config file, mine looks like this:

<add name="MYDBKEY" connectionString="Data Source=LOCALHOST;initial catalog=FubuSample;Integrated Security=SSPI;" providerName="System.Data.SqlClient" />

I also created an empty database in my local SQL Server instance called “FubuSample” And then I went back to SQLServerSessionSourceConfiguration and changed the value of IsNewDatabase to return true. This will create the schema for the database when the application first runs. There is a multitude of different ways that we can handle this, but this was easy for the tutorial purposes.

Next we will add a behavior to our core project and tell FubuMVC to apply that behavior to all or our ControllerActions.

Create a class named “access_the_database_through_a_unit_of_work” in your Core.Web.Behaviors namespace. The contents will look like this:

public class access_the_database_through_a_unit_of_work : IControllerActionBehavior
{
    private readonly IUnitOfWork _unitOfWork;
 
    public access_the_database_through_a_unit_of_work(IUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public IControllerActionBehavior InsideBehavior { get; set; }
    public IInvocationResult Result { get; set; }
 
    public OUTPUT Invoke<INPUT, OUTPUT>(INPUT input, Func<INPUT, OUTPUT> func)
        where INPUT : class
        where OUTPUT : class
    {
        _unitOfWork.Initialize();
 
        try
        {
            var output = InsideBehavior.Invoke(input, func);
            Result = InsideBehavior.Result;
 
            _unitOfWork.Commit();
 
            return output;
        }
        catch
        {
            _unitOfWork.Rollback();
            throw;
        }
        finally
        {
            _unitOfWork.Dispose();
        }
    }
}

Now to tell FubuMVC what to do, open up Global.asax.cs or your Bootstrapper, wherever you are doing the configuration of FubuMVC. In this project we are doing it in Global.asax.cs Add a new behavior to the section that starts with “x.ByDefault.EveryControllerAction” so it looks like this:

x.ByDefault.EveryControllerAction(d =>
   {
       d.Will<execute_the_result>();
       d.Will<access_the_database_through_a_unit_of_work>();
   });

The last thing we will do is open up HomeController and add this code above the Index action:

private IRepository _repository;
 
public HomeController(IRepository repository)
{
    _repository = repository;
}

I also modified the Index action to go ahead and create some database values before we query for them just so we can test this thing. (I only did this for the tutorial, I swear) So modify the Index action to look like this:

public IndexViewModel Index(IndexSetupViewModel inModel)
{
    var prod1 = new Product {Name = "TestProduct1", Description = "This is a test product"};
 
    _repository.Save(prod1);
 
    var prod2 = new Product {Name = "TestProduct2", Description = "This is a test product"};
 
    _repository.Save(prod2);
 
    var outModel = new IndexViewModel();
 
    var productList = _repository.Query<Product>();
 
    outModel.Products = productList.ToList().Select(x => new ProductDisplay(x));
 
    return outModel;
}

Now with you should be able to run your web app and browse to /home and all this will be executed and you will be on your way to creating a whole bunch of persist able objects for use with your FubuMVC app.

As always, feedback is welcome.

]]> http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/feed/ 9 Elegant Code » Blogging http://elegantcode.com Tue, 15 May 2012 10:00:00 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 I guess an introduction is in order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/?utm_source=rss&utm_medium=rss&utm_campaign=i-guess-an-introduction-is-in-order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/#comments Sun, 15 Aug 2010 21:50:26 +0000 Andreas Håkansson http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/ Twitter or from my self-titled blog that I have been blogging on up until this point (and might continue doing, haven’t really made up my mind yet what I am going to do with it). However, my real name is Andreas Håkansson and I guess I could describe myself as a nearly 30 year old .NET developer from Sweden, with a passion for pretty much everything in the software engineering / craftsmanship department (hey, why limit yourself to one kind of cake when there’s so much to be had out there!). I am a strong advocator of Open-Source Software and I head the MEF Contrib project, a set of community contributed extensions, tools and samples for the Managed Extensibility Framework, and I have also created the Common Service Factory, a WCF extension that enabled dependency injection in services (it’s a bit dated, but it works like a charm – probably should give it some love as soon as I can find a slice of spare time in my life). Oh yeah, there’s more to me than being a code ninjah – somehow I’ve also managed to get married to my high school sweetheart (12 years since we hooked up and still going strong) and together we have two wonderful boys (3 and 1½ years old – boy do they know how to keep us busy hehe) Well I guess that’s it… now you know a bit about me, and I hope to get to know a bit more about you, the readers of Elegant Code, so please stop by my posts and drop me a line or two. See you there!]]> http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/feed/ 2 What Does Elegant Code Mean to Me? http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/?utm_source=rss&utm_medium=rss&utm_campaign=what-does-elegant-code-mean-to-me http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/#comments Fri, 09 Apr 2010 19:46:38 +0000 John Sonmez http://elegantcode.com/?p=3434 What is elegance? Simply stated. Something that is simple yet effective, delivered with grace. Being simple is not enough. Simple lacking effectiveness is just a waste of time. Simple - Not Effective Simple, but not effective is a foam hammer. You don't want your code to be like a foam hammer. If it can't do what it supposed to do the simplicity just looks like stupidity instead. Effective, but not simple is something that gets thrown away or lamented. It's a Rube Goldberg machine. Rube Goldberg Machine You don't want your code to be like a Rube Goldberg machine either.  Where people look at your code because it is such a spectacle.  You don't want someone to look at your code and immediately think they want to kill you.  Code that evokes murderous rage, tends to get blamed for anything that goes wrong in the system, even if it works perfectly. If you can build something simple and its effective, it still has to be delivered in a graceful way. Consider, the elephant harness... Simple and Effective - Not Graceful Simple?  Yes, it's a box strapped on top of an Elephant, can't get much more simple than that.  Effective?  Yes, looks to me like that elephant will get you where you need to go in that terrain.  Delivered with grace?  Hmm...  Do you want to ride around on an elephant? Even if you nail the first two, with your code, you should make sure it looks and reads good.  No one wants to ride an elephant.  I have seen more than one simple effective design get thrown away because the variables were named things like "cntr" and "banana".

Elegant Code is James Bond

Women love him, men want to be like him and he kills people with a simple sophistication. When people read your code they should think James Bond, not Booger from Revenge of the Nerds. James-Bond Vs. booger
Elegant code to me is code that reads well, does what is is supposed to do and is easy to maintain. Now that I have told you what I think elegant code is, in future posts I will talk more about how to actually write elegant code.

Side Note - Joining Elegant Code

First of all I wanted to publicly thank the other Elegant Coders for inviting me to join their community. I feel honored and esteemed to be joining such a great group of software craftsmen. I also wanted to clear up confusion for anyone who has been following my blog at http://simpleprogrammer.com.  I will still be blogging there, so don't change your RSS feeds, but in addition I will be blogging here at ElegantCode.com.  If you've come here form a link on my personal blog, I encourage you to check out the other excellent bloggers on this site and consider adding Elegant Code to your RSS feed reader.   My personal blog will contain a wider array of topics, but my content here at ElegantCode.com will be centered around the theme of writing elegant code. As always, feel free to email me at john *dot* sonmez *at* gmail.com or follow me on twitter.]]> http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/feed/ 1 Welcome Two New Elegant Coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/?utm_source=rss&utm_medium=rss&utm_campaign=welcome-two-new-elegant-coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/#comments Thu, 15 Oct 2009 19:58:17 +0000 David Starr http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/ I am happy to introduce 2 new Elegant Coders! We are excited to have their contributions to the site and look forward to their wisdom.

Kirstin Juhl

@kirstinj

We are excited to have Kirstin drop wisdom like she has been doing on her current blog: I [heart] Code. From her own bio:

I am a former engineer who writes code. I did Toyota Operating System, Kanban, and Lean in my factories a decade ago, and am fascinated by its use in software development today. You can take the girl out of the factory, but you cannot take the engineer out of the girl, and so I approach everything in life as a problem to solved or optimized. Including software development. I strive to be a craftsman.

I am a mom, and I take lessons from parenthood into my work everyday.

Jason Jarrett

@staxmanade

Jason is a big-time Silverlight maven and the developer behind StatLight, a set of unit testing tools for Silverlight. I knew he was perfect for the tribe when he said, “… and so I added automocking to Unity for Silverlight.”

Yeah. :)

Welcome all.

]]> http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/feed/ 0 FubuMVC From Scratch – Part 4 Persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/?utm_source=rss&utm_medium=rss&utm_campaign=fubumvc-from-scratch-part-4-persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/#comments Wed, 25 Mar 2009 21:22:00 +0000 Ryan Kelley http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/ Previous posts in series:

Persistence is a requirement in virtually every application that we write today, and now the time has come for us to add a persistence model to our FubuMVC app. I know I mentioned moving my samples to the FubuCart source, but I am going to go ahead and implement the persistence piece in the same project the previous articles using, FubuSample. I have also added all the code for this series to the FubuMVC-Contrib project

We will be implementing our persistence model to use NHibernate, Fluent NHibernate, Repository Pattern and UnitOfWork pattern all on top of SQL Express or standard. This will also work for sqllite and other database servers.

Class and Interfaces we have to implement:

  • ISessionSourceConfiguration
  • SQLServerSessionSourceConfiguration
  • IUnitOfWork
  • INHibernateUnitOfWork
  • NHibernateUnitOfWork
  • IRepository
  • NHibernateRepository
  • DomainEntity
  • IDomainQuery
  • FubuSamplePersistenceModel

Note: I put the first two in the list in my Core.Config namespace, and the rest in Core.Persistence

Before we start you probably want to go ahead and add the following references to your core project and Web project

FubuMVC-Persist-Ref

Let’s just work our way down the list and get these files implemented.

ISessionSourceConfiguration

public interface ISessionSourceConfiguration
{
    bool IsNewDatabase { get; }
    ISessionSource CreateSessionSource(PersistenceModel model);
}

SQLServerSessionSourceConfiguration

public class SQLServerSessionSourceConfiguration : ISessionSourceConfiguration
{
    #region Implementation of ISessionSourceConfiguration
 
    public bool IsNewDatabase
    {
        get { return false; }
    }
 
    public ISessionSource CreateSessionSource(PersistenceModel model)
    {
        var properties = GetProperties();
        var source = new SessionSource(properties, model);
 
        create_schema_if_it_does_not_already_exist(source);
 
        return source;
    }
 
    private void create_schema_if_it_does_not_already_exist(ISessionSource source)
    {
        if (IsNewDatabase) source.BuildSchema();
    }
 
    protected IDictionary<string, string> GetProperties()
    {
        MsSqlConfiguration config = MsSqlConfiguration.MsSql2005;
        config.ConnectionString.FromConnectionStringWithKey(“MYDBKEY”);
        config.ShowSql();
        config.UseOuterJoin();
 
        return config.ToProperties();
    }
    #endregion
}

A quick note here: We told SQLServerSessionSourceConfiguration to use a connection string from the app settings file (Web.Config) with a key of “MYDBKEY” This will be important later.

IUnitOfWork

public interface IUnitOfWork : IDisposable
{
    void Initialize();
    void Commit();
    void Rollback();
}

INHibernateUnitOfWork

public interface INHibernateUnitOfWork : IUnitOfWork
{
    ISession CurrentSession { get; }
}

NHibernateUnitOfWork

public class NHibernateUnitOfWork : INHibernateUnitOfWork
{
    private ITransaction _transaction;
    private bool _isDisposed;
    private readonly ISessionSource _source;
    private bool _isInitialized;
 
    public NHibernateUnitOfWork(ISessionSource source)
    {
        _source = source;
    }
 
    public void Initialize()
    {
        should_not_currently_be_disposed();
 
        CurrentSession = _source.CreateSession();
        begin_new_transaction();
 
        _isInitialized = true;
    }
 
    public ISession CurrentSession { get; private set; }
 
    public void Commit()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Commit();
 
        begin_new_transaction();
    }
 
    private void begin_new_transaction()
    {
        if (_transaction != null)
        {
            _transaction.Dispose();
        }
 
        _transaction = CurrentSession.BeginTransaction();
    }
 
    public void Rollback()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Rollback();
 
        begin_new_transaction();
    }
 
    private void should_not_currently_be_disposed()
    {
        if (_isDisposed) throw new ObjectDisposedException(GetType().Name);
    }
 
    private void should_be_initialized_first()
    {
        if (!_isInitialized) throw new InvalidOperationException("Must initialize (call Initialize()) on NHibernateUnitOfWork before commiting or rolling back");
    }
 
    public void Dispose()
    {
        if (_isDisposed || !_isInitialized) return;
 
        _transaction.Dispose();
        CurrentSession.Dispose();
 
        _isDisposed = true;
    }
}

IRepository

public interface IRepository
{
    void Save<ENTITY>(ENTITY entity)
        where ENTITY : DomainEntity;
 
    ENTITY Load<ENTITY>(Guid id)
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>()
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery)
        where ENTITY : DomainEntity;
 
    void Delete<ENTITY>(ENTITY entity);
 
    void DeleteAll<ENTITY>();
}

NHibernateRepository

public class NHibernateRepository : IRepository
{
    private readonly INHibernateUnitOfWork _unitOfWork;
 
    public NHibernateRepository(INHibernateUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public void Save<ENTITY>(ENTITY entity) where ENTITY : DomainEntity
    {
        _unitOfWork.CurrentSession.SaveOrUpdate(entity);
    }
 
    public ENTITY Load<ENTITY>(Guid id) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Load<ENTITY>(id);
    }
 
    public IQueryable<ENTITY> Query<ENTITY>() where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>();
    }
 
    public IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>().Where(whereQuery.Expression);
    }
 
    public void Delete<ENTITY>(ENTITY entity)
    {
        _unitOfWork.CurrentSession.Delete(entity);   
    }
 
    public void DeleteAll<ENTITY>()
    {
        var query = String.Format("from {0}", typeof(ENTITY).Name);
        _unitOfWork.CurrentSession.Delete(query);   
    }
}

DomainEntity

Note: I put both of these classes in my Core.Domain namespace, also XML comments are in Source Repository

public class DomainEntity : IEquatable<DomainEntity>
{
    public virtual Guid ID { get; set; }
 
    public virtual bool Equals(DomainEntity other)
    {
        if (ReferenceEquals(null, other)) return false;
        if (ReferenceEquals(this, other)) return true;
        return other.ID.Equals(ID);
    }
 
    public override bool Equals(object obj)
    {
        if (ReferenceEquals(null, obj)) return false;
        if (ReferenceEquals(this, obj)) return true;
        if (obj.GetType() != GetType()) return false;
        return Equals((DomainEntity)obj);
    }
 
    public override int GetHashCode()
    {
        return ID.GetHashCode();
    }
 
    public static bool operator ==(DomainEntity left, DomainEntity right)
    {
        return Equals(left, right);
    }
 
    public static bool operator !=(DomainEntity left, DomainEntity right)
    {
        return !Equals(left, right);
    }
}

IDomainQuery

public interface IDomainQuery<ENTITY>
    where ENTITY : DomainEntity
{
    Expression<Func<ENTITY, bool>> Expression { get; }
}

FubuSamplePersistenceModel

namespace FubuSample.Core.Domain.Persistence
{
    public class FubuSamplePersistenceModel : PersistenceModel
    {
        public FubuSamplePersistenceModel()
        {
            addMappingsFromThisAssembly();
        }
    }
}

Now that we have all the puzzle pieces in place we need to hook them up and make them do some work. Open up FubuSampleWebRegistry

And add the following code:

protected override void configure()
{
    ForRequestedType<ISessionSourceConfiguration>().AsSingletons()
        .TheDefault.Is.OfConcreteType<SQLServerSessionSourceConfiguration>();
 
 
    ForRequestedType<ISessionSource>().AsSingletons()
        .TheDefault.Is.ConstructedBy(ctx =>
                                     ctx.GetInstance<ISessionSourceConfiguration>()
                                         .CreateSessionSource(new FubuSamplePersistenceModel()));
 
    ForRequestedType<IUnitOfWork>().TheDefault.Is.ConstructedBy(ctx => ctx.GetInstance<INHibernateUnitOfWork>());
 
    ForRequestedType<INHibernateUnitOfWork>().CacheBy(InstanceScope.Hybrid)
        .TheDefault.Is.OfConcreteType<NHibernateUnitOfWork>();
 
    ForRequestedType<IRepository>().TheDefault.Is.OfConcreteType<NHibernateRepository>();
}

With a little luck and all of our mad skills, we should be able to talk to the database now. So we need to plumb our simple product object up to talk to NHibernate. We will do this with a mapping file, and since we are using FluentNHibernate we can do this strongly typed.

Make the following modifications to Product: Extend DomainEntity and get rid of Id Property, it is inherited

public class Product : DomainEntity
{
    public virtual string Name { get; set; }
    public virtual string Description { get; set; }
}

Add mapping file for Product:

namespace FubuSample.Core.Domain.Mapping
{
    public class ProductMap : ClassMap<Product>
    {
        public ProductMap()
        {
            Id(e => e.ID).GeneratedBy.GuidComb();
 
            Map(p => p.Name);
            Map(p => p.Description);
            
        }
    }
}

You may also want to setup your connection string at this point in the Web.Config file, mine looks like this:

<add name="MYDBKEY" connectionString="Data Source=LOCALHOST;initial catalog=FubuSample;Integrated Security=SSPI;" providerName="System.Data.SqlClient" />

I also created an empty database in my local SQL Server instance called “FubuSample” And then I went back to SQLServerSessionSourceConfiguration and changed the value of IsNewDatabase to return true. This will create the schema for the database when the application first runs. There is a multitude of different ways that we can handle this, but this was easy for the tutorial purposes.

Next we will add a behavior to our core project and tell FubuMVC to apply that behavior to all or our ControllerActions.

Create a class named “access_the_database_through_a_unit_of_work” in your Core.Web.Behaviors namespace. The contents will look like this:

public class access_the_database_through_a_unit_of_work : IControllerActionBehavior
{
    private readonly IUnitOfWork _unitOfWork;
 
    public access_the_database_through_a_unit_of_work(IUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public IControllerActionBehavior InsideBehavior { get; set; }
    public IInvocationResult Result { get; set; }
 
    public OUTPUT Invoke<INPUT, OUTPUT>(INPUT input, Func<INPUT, OUTPUT> func)
        where INPUT : class
        where OUTPUT : class
    {
        _unitOfWork.Initialize();
 
        try
        {
            var output = InsideBehavior.Invoke(input, func);
            Result = InsideBehavior.Result;
 
            _unitOfWork.Commit();
 
            return output;
        }
        catch
        {
            _unitOfWork.Rollback();
            throw;
        }
        finally
        {
            _unitOfWork.Dispose();
        }
    }
}

Now to tell FubuMVC what to do, open up Global.asax.cs or your Bootstrapper, wherever you are doing the configuration of FubuMVC. In this project we are doing it in Global.asax.cs Add a new behavior to the section that starts with “x.ByDefault.EveryControllerAction” so it looks like this:

x.ByDefault.EveryControllerAction(d =>
   {
       d.Will<execute_the_result>();
       d.Will<access_the_database_through_a_unit_of_work>();
   });

The last thing we will do is open up HomeController and add this code above the Index action:

private IRepository _repository;
 
public HomeController(IRepository repository)
{
    _repository = repository;
}

I also modified the Index action to go ahead and create some database values before we query for them just so we can test this thing. (I only did this for the tutorial, I swear) So modify the Index action to look like this:

public IndexViewModel Index(IndexSetupViewModel inModel)
{
    var prod1 = new Product {Name = "TestProduct1", Description = "This is a test product"};
 
    _repository.Save(prod1);
 
    var prod2 = new Product {Name = "TestProduct2", Description = "This is a test product"};
 
    _repository.Save(prod2);
 
    var outModel = new IndexViewModel();
 
    var productList = _repository.Query<Product>();
 
    outModel.Products = productList.ToList().Select(x => new ProductDisplay(x));
 
    return outModel;
}

Now with you should be able to run your web app and browse to /home and all this will be executed and you will be on your way to creating a whole bunch of persist able objects for use with your FubuMVC app.

As always, feedback is welcome.

]]> http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/feed/ 9 It’s Official – New Gig started last week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/?utm_source=rss&utm_medium=rss&utm_campaign=its-official-new-gig-started-last-week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/#comments Tue, 24 Feb 2009 19:03:21 +0000 Ryan Kelley http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/ CoachesAid.com. CoachesAid is a High School sports website that is expanding rapidly and it is my task to make this expansion happen as smoothly and as quickly as possible. The past month has been very hectic as I was wrapping up loose ends at my previous engagement. I started my new gig last week, but I have pretty much been building furniture and getting computer and server ready to go. The next few weeks will also be challenging as I start to assemble the team of people that is going to make this all happen. How does this tie into the practice of Elegant Coding? Funny you should ask that, the current infrastructure they are built on is a maintenance nightmare so project number one is to completely redo their entire site infrastructure in ASP.Net, and yes it will be MVC based, but not ASP.Net MVC. I am going to architect and build their new infrastructure from the ground up on FubuMVC. So expect a lot more posts from me on FubuMVC and I may even have questions for you dear reader. Side Note: I just finished deploying to production a small scale site built on FubuMVC, and it ROCKS! There is going to be some stuff that needs to be tweaked out and added to the core, but overall, fully functional MVC framework. I hope I haven’t bored you with too much personal information, but I have to go. (I have several FubuMVC posts stacked up in my queue) -Ryan]]> http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/feed/ 8 Quick 2008 Recap and a few New Years Resolutions http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/?utm_source=rss&utm_medium=rss&utm_campaign=quick-2008-recap-and-a-few-new-years-resolutions http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/#comments Thu, 01 Jan 2009 15:57:06 +0000 Ryan Kelley http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/ Whew, I cannot believe that 2008 is over already, it seems like it just started. 2008 was a great year for me as a developer for several reasons.

Met new People

I was able to meet a ton of new people in 2008, both online through blogs and other communities, and at KaizenConf in Austin. This is probably the single most important thing that happened to me in 2008 because it helped put me into circle of people that share the same thoughts and values about software development that I do.

Alt.Net Introduction

I was also introduced to the Alt.Net movement during 2008. I have been developing software for several years and some of the things I had been doing just didn’t seem quite right, they worked, but they had a smell to them. Enter Alt.Net, this stuff just makes sense. It is smart software development, that revolves around creating highly testable, highly maintainable code that follows the SOLID design principles. I have come to realize that if you just ask yourself “How does this proposed solution adhere to the SOLID principles” you will write much more elegant code.

KaizenConf Open Spaces Conference

This was my first open spaces conference and I didn’t know what to expect but I came away with the feeling that this was the best conference I had ever been to. KaizenConf helped fuel my fire for continuing with more Alt.Net stuff, working on Lean Software Development and KanBan methods, and staying involved with the community. It even spurred me to start blogging more frequently about these topics.

Some 2009 Resolutions

I have a few resolutions I am going to make for the new year, some are computer related, some are not.

  • Blog More – I am targeting 52 blog posts in 2009, that is a little more than double from 2008 and is only 1 per week.
  • Fish more, I love fly fishing, just need to make more time
    • Fly Fish for Bass – talk about fun!
  • Write Elegant Code – I am staying committed to SOLID principles, testability and maintainable code.
  • Learn more about Asp.Net – Especially MVC stuff, I have been doing WinForms development for the past 4 years, so I am looking forward to this one.
  • Learn a new Programming Language – Everybody should do this every year.

I am going to stop there, I don’t want to set any unrealistic expectations for myself during the year. I think all of these are very attainable and I hope that my list has spurred some inner resolution making within you to go out and commit to something new in 2009.

]]> http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/feed/ 2 Hello Elegant Code Readers http://elegantcode.com/2008/12/02/hello-elegant-code-readers/?utm_source=rss&utm_medium=rss&utm_campaign=hello-elegant-code-readers http://elegantcode.com/2008/12/02/hello-elegant-code-readers/#comments Tue, 02 Dec 2008 15:18:27 +0000 Ryan Kelley http://elegantcode.com/2008/12/02/hello-elegant-code-readers/ As Jarod Ferguson already mentioned, I am now part of the Elegant Code team. I must say it is an honor to be invited to join this community and I am very excited about this opportunity. I will still cross-post on my own blog as well as here on elegantcode.com.

I am a pretty easy going guy, so hopefully this opportunity will spur me into posting with more regularity. If anybody has any topics they want me to write about just drop me a line.

One last thing, Thank You to all the Elegant Coders for giving me the invite.

]]> http://elegantcode.com/2008/12/02/hello-elegant-code-readers/feed/ 3 Joining Elegant Code http://elegantcode.com/2008/11/22/joining-elegant-code/?utm_source=rss&utm_medium=rss&utm_campaign=joining-elegant-code http://elegantcode.com/2008/11/22/joining-elegant-code/#comments Sun, 23 Nov 2008 00:52:53 +0000 Guest Blogger http://elegantcode.com/?p=1545 mentioned, i am now part of the Elegant Code team. It's an honor to be invited and i'm obviously very happy with this. All of my posts will still be posted to my own blog, as well as on elegantcode.com. And the NHibernate posts will also continue to be cross posted to NHForge. Now if you'll excuse me, i've got to start writing some posts ;)]]> http://elegantcode.com/2008/11/22/joining-elegant-code/feed/ 2 The New Blogger Toolkit http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/?utm_source=rss&utm_medium=rss&utm_campaign=its-official-new-gig-started-last-week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/#comments Tue, 24 Feb 2009 19:03:21 +0000 Ryan Kelley http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/ CoachesAid.com. CoachesAid is a High School sports website that is expanding rapidly and it is my task to make this expansion happen as smoothly and as quickly as possible. The past month has been very hectic as I was wrapping up loose ends at my previous engagement. I started my new gig last week, but I have pretty much been building furniture and getting computer and server ready to go. The next few weeks will also be challenging as I start to assemble the team of people that is going to make this all happen. How does this tie into the practice of Elegant Coding? Funny you should ask that, the current infrastructure they are built on is a maintenance nightmare so project number one is to completely redo their entire site infrastructure in ASP.Net, and yes it will be MVC based, but not ASP.Net MVC. I am going to architect and build their new infrastructure from the ground up on FubuMVC. So expect a lot more posts from me on FubuMVC and I may even have questions for you dear reader. Side Note: I just finished deploying to production a small scale site built on FubuMVC, and it ROCKS! There is going to be some stuff that needs to be tweaked out and added to the core, but overall, fully functional MVC framework. I hope I haven’t bored you with too much personal information, but I have to go. (I have several FubuMVC posts stacked up in my queue) -Ryan]]> http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/feed/ 8 Elegant Code » Blogging http://elegantcode.com Tue, 15 May 2012 10:00:00 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 I guess an introduction is in order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/?utm_source=rss&utm_medium=rss&utm_campaign=i-guess-an-introduction-is-in-order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/#comments Sun, 15 Aug 2010 21:50:26 +0000 Andreas Håkansson http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/ Twitter or from my self-titled blog that I have been blogging on up until this point (and might continue doing, haven’t really made up my mind yet what I am going to do with it). However, my real name is Andreas Håkansson and I guess I could describe myself as a nearly 30 year old .NET developer from Sweden, with a passion for pretty much everything in the software engineering / craftsmanship department (hey, why limit yourself to one kind of cake when there’s so much to be had out there!). I am a strong advocator of Open-Source Software and I head the MEF Contrib project, a set of community contributed extensions, tools and samples for the Managed Extensibility Framework, and I have also created the Common Service Factory, a WCF extension that enabled dependency injection in services (it’s a bit dated, but it works like a charm – probably should give it some love as soon as I can find a slice of spare time in my life). Oh yeah, there’s more to me than being a code ninjah – somehow I’ve also managed to get married to my high school sweetheart (12 years since we hooked up and still going strong) and together we have two wonderful boys (3 and 1½ years old – boy do they know how to keep us busy hehe) Well I guess that’s it… now you know a bit about me, and I hope to get to know a bit more about you, the readers of Elegant Code, so please stop by my posts and drop me a line or two. See you there!]]> http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/feed/ 2 What Does Elegant Code Mean to Me? http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/?utm_source=rss&utm_medium=rss&utm_campaign=what-does-elegant-code-mean-to-me http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/#comments Fri, 09 Apr 2010 19:46:38 +0000 John Sonmez http://elegantcode.com/?p=3434 What is elegance? Simply stated. Something that is simple yet effective, delivered with grace. Being simple is not enough. Simple lacking effectiveness is just a waste of time. Simple - Not Effective Simple, but not effective is a foam hammer. You don't want your code to be like a foam hammer. If it can't do what it supposed to do the simplicity just looks like stupidity instead. Effective, but not simple is something that gets thrown away or lamented. It's a Rube Goldberg machine. Rube Goldberg Machine You don't want your code to be like a Rube Goldberg machine either.  Where people look at your code because it is such a spectacle.  You don't want someone to look at your code and immediately think they want to kill you.  Code that evokes murderous rage, tends to get blamed for anything that goes wrong in the system, even if it works perfectly. If you can build something simple and its effective, it still has to be delivered in a graceful way. Consider, the elephant harness... Simple and Effective - Not Graceful Simple?  Yes, it's a box strapped on top of an Elephant, can't get much more simple than that.  Effective?  Yes, looks to me like that elephant will get you where you need to go in that terrain.  Delivered with grace?  Hmm...  Do you want to ride around on an elephant? Even if you nail the first two, with your code, you should make sure it looks and reads good.  No one wants to ride an elephant.  I have seen more than one simple effective design get thrown away because the variables were named things like "cntr" and "banana".

Elegant Code is James Bond

Women love him, men want to be like him and he kills people with a simple sophistication. When people read your code they should think James Bond, not Booger from Revenge of the Nerds. James-Bond Vs. booger
Elegant code to me is code that reads well, does what is is supposed to do and is easy to maintain. Now that I have told you what I think elegant code is, in future posts I will talk more about how to actually write elegant code.

Side Note - Joining Elegant Code

First of all I wanted to publicly thank the other Elegant Coders for inviting me to join their community. I feel honored and esteemed to be joining such a great group of software craftsmen. I also wanted to clear up confusion for anyone who has been following my blog at http://simpleprogrammer.com.  I will still be blogging there, so don't change your RSS feeds, but in addition I will be blogging here at ElegantCode.com.  If you've come here form a link on my personal blog, I encourage you to check out the other excellent bloggers on this site and consider adding Elegant Code to your RSS feed reader.   My personal blog will contain a wider array of topics, but my content here at ElegantCode.com will be centered around the theme of writing elegant code. As always, feel free to email me at john *dot* sonmez *at* gmail.com or follow me on twitter.]]> http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/feed/ 1 Welcome Two New Elegant Coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/?utm_source=rss&utm_medium=rss&utm_campaign=welcome-two-new-elegant-coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/#comments Thu, 15 Oct 2009 19:58:17 +0000 David Starr http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/ I am happy to introduce 2 new Elegant Coders! We are excited to have their contributions to the site and look forward to their wisdom.

Kirstin Juhl

@kirstinj

We are excited to have Kirstin drop wisdom like she has been doing on her current blog: I [heart] Code. From her own bio:

I am a former engineer who writes code. I did Toyota Operating System, Kanban, and Lean in my factories a decade ago, and am fascinated by its use in software development today. You can take the girl out of the factory, but you cannot take the engineer out of the girl, and so I approach everything in life as a problem to solved or optimized. Including software development. I strive to be a craftsman.

I am a mom, and I take lessons from parenthood into my work everyday.

Jason Jarrett

@staxmanade

Jason is a big-time Silverlight maven and the developer behind StatLight, a set of unit testing tools for Silverlight. I knew he was perfect for the tribe when he said, “… and so I added automocking to Unity for Silverlight.”

Yeah. :)

Welcome all.

]]> http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/feed/ 0 FubuMVC From Scratch – Part 4 Persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/?utm_source=rss&utm_medium=rss&utm_campaign=fubumvc-from-scratch-part-4-persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/#comments Wed, 25 Mar 2009 21:22:00 +0000 Ryan Kelley http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/ Previous posts in series:

Persistence is a requirement in virtually every application that we write today, and now the time has come for us to add a persistence model to our FubuMVC app. I know I mentioned moving my samples to the FubuCart source, but I am going to go ahead and implement the persistence piece in the same project the previous articles using, FubuSample. I have also added all the code for this series to the FubuMVC-Contrib project

We will be implementing our persistence model to use NHibernate, Fluent NHibernate, Repository Pattern and UnitOfWork pattern all on top of SQL Express or standard. This will also work for sqllite and other database servers.

Class and Interfaces we have to implement:

  • ISessionSourceConfiguration
  • SQLServerSessionSourceConfiguration
  • IUnitOfWork
  • INHibernateUnitOfWork
  • NHibernateUnitOfWork
  • IRepository
  • NHibernateRepository
  • DomainEntity
  • IDomainQuery
  • FubuSamplePersistenceModel

Note: I put the first two in the list in my Core.Config namespace, and the rest in Core.Persistence

Before we start you probably want to go ahead and add the following references to your core project and Web project

FubuMVC-Persist-Ref

Let’s just work our way down the list and get these files implemented.

ISessionSourceConfiguration

public interface ISessionSourceConfiguration
{
    bool IsNewDatabase { get; }
    ISessionSource CreateSessionSource(PersistenceModel model);
}

SQLServerSessionSourceConfiguration

public class SQLServerSessionSourceConfiguration : ISessionSourceConfiguration
{
    #region Implementation of ISessionSourceConfiguration
 
    public bool IsNewDatabase
    {
        get { return false; }
    }
 
    public ISessionSource CreateSessionSource(PersistenceModel model)
    {
        var properties = GetProperties();
        var source = new SessionSource(properties, model);
 
        create_schema_if_it_does_not_already_exist(source);
 
        return source;
    }
 
    private void create_schema_if_it_does_not_already_exist(ISessionSource source)
    {
        if (IsNewDatabase) source.BuildSchema();
    }
 
    protected IDictionary<string, string> GetProperties()
    {
        MsSqlConfiguration config = MsSqlConfiguration.MsSql2005;
        config.ConnectionString.FromConnectionStringWithKey(“MYDBKEY”);
        config.ShowSql();
        config.UseOuterJoin();
 
        return config.ToProperties();
    }
    #endregion
}

A quick note here: We told SQLServerSessionSourceConfiguration to use a connection string from the app settings file (Web.Config) with a key of “MYDBKEY” This will be important later.

IUnitOfWork

public interface IUnitOfWork : IDisposable
{
    void Initialize();
    void Commit();
    void Rollback();
}

INHibernateUnitOfWork

public interface INHibernateUnitOfWork : IUnitOfWork
{
    ISession CurrentSession { get; }
}

NHibernateUnitOfWork

public class NHibernateUnitOfWork : INHibernateUnitOfWork
{
    private ITransaction _transaction;
    private bool _isDisposed;
    private readonly ISessionSource _source;
    private bool _isInitialized;
 
    public NHibernateUnitOfWork(ISessionSource source)
    {
        _source = source;
    }
 
    public void Initialize()
    {
        should_not_currently_be_disposed();
 
        CurrentSession = _source.CreateSession();
        begin_new_transaction();
 
        _isInitialized = true;
    }
 
    public ISession CurrentSession { get; private set; }
 
    public void Commit()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Commit();
 
        begin_new_transaction();
    }
 
    private void begin_new_transaction()
    {
        if (_transaction != null)
        {
            _transaction.Dispose();
        }
 
        _transaction = CurrentSession.BeginTransaction();
    }
 
    public void Rollback()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Rollback();
 
        begin_new_transaction();
    }
 
    private void should_not_currently_be_disposed()
    {
        if (_isDisposed) throw new ObjectDisposedException(GetType().Name);
    }
 
    private void should_be_initialized_first()
    {
        if (!_isInitialized) throw new InvalidOperationException("Must initialize (call Initialize()) on NHibernateUnitOfWork before commiting or rolling back");
    }
 
    public void Dispose()
    {
        if (_isDisposed || !_isInitialized) return;
 
        _transaction.Dispose();
        CurrentSession.Dispose();
 
        _isDisposed = true;
    }
}

IRepository

public interface IRepository
{
    void Save<ENTITY>(ENTITY entity)
        where ENTITY : DomainEntity;
 
    ENTITY Load<ENTITY>(Guid id)
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>()
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery)
        where ENTITY : DomainEntity;
 
    void Delete<ENTITY>(ENTITY entity);
 
    void DeleteAll<ENTITY>();
}

NHibernateRepository

public class NHibernateRepository : IRepository
{
    private readonly INHibernateUnitOfWork _unitOfWork;
 
    public NHibernateRepository(INHibernateUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public void Save<ENTITY>(ENTITY entity) where ENTITY : DomainEntity
    {
        _unitOfWork.CurrentSession.SaveOrUpdate(entity);
    }
 
    public ENTITY Load<ENTITY>(Guid id) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Load<ENTITY>(id);
    }
 
    public IQueryable<ENTITY> Query<ENTITY>() where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>();
    }
 
    public IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>().Where(whereQuery.Expression);
    }
 
    public void Delete<ENTITY>(ENTITY entity)
    {
        _unitOfWork.CurrentSession.Delete(entity);   
    }
 
    public void DeleteAll<ENTITY>()
    {
        var query = String.Format("from {0}", typeof(ENTITY).Name);
        _unitOfWork.CurrentSession.Delete(query);   
    }
}

DomainEntity

Note: I put both of these classes in my Core.Domain namespace, also XML comments are in Source Repository

public class DomainEntity : IEquatable<DomainEntity>
{
    public virtual Guid ID { get; set; }
 
    public virtual bool Equals(DomainEntity other)
    {
        if (ReferenceEquals(null, other)) return false;
        if (ReferenceEquals(this, other)) return true;
        return other.ID.Equals(ID);
    }
 
    public override bool Equals(object obj)
    {
        if (ReferenceEquals(null, obj)) return false;
        if (ReferenceEquals(this, obj)) return true;
        if (obj.GetType() != GetType()) return false;
        return Equals((DomainEntity)obj);
    }
 
    public override int GetHashCode()
    {
        return ID.GetHashCode();
    }
 
    public static bool operator ==(DomainEntity left, DomainEntity right)
    {
        return Equals(left, right);
    }
 
    public static bool operator !=(DomainEntity left, DomainEntity right)
    {
        return !Equals(left, right);
    }
}

IDomainQuery

public interface IDomainQuery<ENTITY>
    where ENTITY : DomainEntity
{
    Expression<Func<ENTITY, bool>> Expression { get; }
}

FubuSamplePersistenceModel

namespace FubuSample.Core.Domain.Persistence
{
    public class FubuSamplePersistenceModel : PersistenceModel
    {
        public FubuSamplePersistenceModel()
        {
            addMappingsFromThisAssembly();
        }
    }
}

Now that we have all the puzzle pieces in place we need to hook them up and make them do some work. Open up FubuSampleWebRegistry

And add the following code:

protected override void configure()
{
    ForRequestedType<ISessionSourceConfiguration>().AsSingletons()
        .TheDefault.Is.OfConcreteType<SQLServerSessionSourceConfiguration>();
 
 
    ForRequestedType<ISessionSource>().AsSingletons()
        .TheDefault.Is.ConstructedBy(ctx =>
                                     ctx.GetInstance<ISessionSourceConfiguration>()
                                         .CreateSessionSource(new FubuSamplePersistenceModel()));
 
    ForRequestedType<IUnitOfWork>().TheDefault.Is.ConstructedBy(ctx => ctx.GetInstance<INHibernateUnitOfWork>());
 
    ForRequestedType<INHibernateUnitOfWork>().CacheBy(InstanceScope.Hybrid)
        .TheDefault.Is.OfConcreteType<NHibernateUnitOfWork>();
 
    ForRequestedType<IRepository>().TheDefault.Is.OfConcreteType<NHibernateRepository>();
}

With a little luck and all of our mad skills, we should be able to talk to the database now. So we need to plumb our simple product object up to talk to NHibernate. We will do this with a mapping file, and since we are using FluentNHibernate we can do this strongly typed.

Make the following modifications to Product: Extend DomainEntity and get rid of Id Property, it is inherited

public class Product : DomainEntity
{
    public virtual string Name { get; set; }
    public virtual string Description { get; set; }
}

Add mapping file for Product:

namespace FubuSample.Core.Domain.Mapping
{
    public class ProductMap : ClassMap<Product>
    {
        public ProductMap()
        {
            Id(e => e.ID).GeneratedBy.GuidComb();
 
            Map(p => p.Name);
            Map(p => p.Description);
            
        }
    }
}

You may also want to setup your connection string at this point in the Web.Config file, mine looks like this:

<add name="MYDBKEY" connectionString="Data Source=LOCALHOST;initial catalog=FubuSample;Integrated Security=SSPI;" providerName="System.Data.SqlClient" />

I also created an empty database in my local SQL Server instance called “FubuSample” And then I went back to SQLServerSessionSourceConfiguration and changed the value of IsNewDatabase to return true. This will create the schema for the database when the application first runs. There is a multitude of different ways that we can handle this, but this was easy for the tutorial purposes.

Next we will add a behavior to our core project and tell FubuMVC to apply that behavior to all or our ControllerActions.

Create a class named “access_the_database_through_a_unit_of_work” in your Core.Web.Behaviors namespace. The contents will look like this:

public class access_the_database_through_a_unit_of_work : IControllerActionBehavior
{
    private readonly IUnitOfWork _unitOfWork;
 
    public access_the_database_through_a_unit_of_work(IUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public IControllerActionBehavior InsideBehavior { get; set; }
    public IInvocationResult Result { get; set; }
 
    public OUTPUT Invoke<INPUT, OUTPUT>(INPUT input, Func<INPUT, OUTPUT> func)
        where INPUT : class
        where OUTPUT : class
    {
        _unitOfWork.Initialize();
 
        try
        {
            var output = InsideBehavior.Invoke(input, func);
            Result = InsideBehavior.Result;
 
            _unitOfWork.Commit();
 
            return output;
        }
        catch
        {
            _unitOfWork.Rollback();
            throw;
        }
        finally
        {
            _unitOfWork.Dispose();
        }
    }
}

Now to tell FubuMVC what to do, open up Global.asax.cs or your Bootstrapper, wherever you are doing the configuration of FubuMVC. In this project we are doing it in Global.asax.cs Add a new behavior to the section that starts with “x.ByDefault.EveryControllerAction” so it looks like this:

x.ByDefault.EveryControllerAction(d =>
   {
       d.Will<execute_the_result>();
       d.Will<access_the_database_through_a_unit_of_work>();
   });

The last thing we will do is open up HomeController and add this code above the Index action:

private IRepository _repository;
 
public HomeController(IRepository repository)
{
    _repository = repository;
}

I also modified the Index action to go ahead and create some database values before we query for them just so we can test this thing. (I only did this for the tutorial, I swear) So modify the Index action to look like this:

public IndexViewModel Index(IndexSetupViewModel inModel)
{
    var prod1 = new Product {Name = "TestProduct1", Description = "This is a test product"};
 
    _repository.Save(prod1);
 
    var prod2 = new Product {Name = "TestProduct2", Description = "This is a test product"};
 
    _repository.Save(prod2);
 
    var outModel = new IndexViewModel();
 
    var productList = _repository.Query<Product>();
 
    outModel.Products = productList.ToList().Select(x => new ProductDisplay(x));
 
    return outModel;
}

Now with you should be able to run your web app and browse to /home and all this will be executed and you will be on your way to creating a whole bunch of persist able objects for use with your FubuMVC app.

As always, feedback is welcome.

]]> http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/feed/ 9 It’s Official – New Gig started last week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/?utm_source=rss&utm_medium=rss&utm_campaign=its-official-new-gig-started-last-week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/#comments Tue, 24 Feb 2009 19:03:21 +0000 Ryan Kelley http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/ CoachesAid.com. CoachesAid is a High School sports website that is expanding rapidly and it is my task to make this expansion happen as smoothly and as quickly as possible. The past month has been very hectic as I was wrapping up loose ends at my previous engagement. I started my new gig last week, but I have pretty much been building furniture and getting computer and server ready to go. The next few weeks will also be challenging as I start to assemble the team of people that is going to make this all happen. How does this tie into the practice of Elegant Coding? Funny you should ask that, the current infrastructure they are built on is a maintenance nightmare so project number one is to completely redo their entire site infrastructure in ASP.Net, and yes it will be MVC based, but not ASP.Net MVC. I am going to architect and build their new infrastructure from the ground up on FubuMVC. So expect a lot more posts from me on FubuMVC and I may even have questions for you dear reader. Side Note: I just finished deploying to production a small scale site built on FubuMVC, and it ROCKS! There is going to be some stuff that needs to be tweaked out and added to the core, but overall, fully functional MVC framework. I hope I haven’t bored you with too much personal information, but I have to go. (I have several FubuMVC posts stacked up in my queue) -Ryan]]> http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/feed/ 8 Quick 2008 Recap and a few New Years Resolutions http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/?utm_source=rss&utm_medium=rss&utm_campaign=quick-2008-recap-and-a-few-new-years-resolutions http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/#comments Thu, 01 Jan 2009 15:57:06 +0000 Ryan Kelley http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/ Whew, I cannot believe that 2008 is over already, it seems like it just started. 2008 was a great year for me as a developer for several reasons.

Met new People

I was able to meet a ton of new people in 2008, both online through blogs and other communities, and at KaizenConf in Austin. This is probably the single most important thing that happened to me in 2008 because it helped put me into circle of people that share the same thoughts and values about software development that I do.

Alt.Net Introduction

I was also introduced to the Alt.Net movement during 2008. I have been developing software for several years and some of the things I had been doing just didn’t seem quite right, they worked, but they had a smell to them. Enter Alt.Net, this stuff just makes sense. It is smart software development, that revolves around creating highly testable, highly maintainable code that follows the SOLID design principles. I have come to realize that if you just ask yourself “How does this proposed solution adhere to the SOLID principles” you will write much more elegant code.

KaizenConf Open Spaces Conference

This was my first open spaces conference and I didn’t know what to expect but I came away with the feeling that this was the best conference I had ever been to. KaizenConf helped fuel my fire for continuing with more Alt.Net stuff, working on Lean Software Development and KanBan methods, and staying involved with the community. It even spurred me to start blogging more frequently about these topics.

Some 2009 Resolutions

I have a few resolutions I am going to make for the new year, some are computer related, some are not.

  • Blog More – I am targeting 52 blog posts in 2009, that is a little more than double from 2008 and is only 1 per week.
  • Fish more, I love fly fishing, just need to make more time
    • Fly Fish for Bass – talk about fun!
  • Write Elegant Code – I am staying committed to SOLID principles, testability and maintainable code.
  • Learn more about Asp.Net – Especially MVC stuff, I have been doing WinForms development for the past 4 years, so I am looking forward to this one.
  • Learn a new Programming Language – Everybody should do this every year.

I am going to stop there, I don’t want to set any unrealistic expectations for myself during the year. I think all of these are very attainable and I hope that my list has spurred some inner resolution making within you to go out and commit to something new in 2009.

]]> http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/feed/ 2 Hello Elegant Code Readers http://elegantcode.com/2008/12/02/hello-elegant-code-readers/?utm_source=rss&utm_medium=rss&utm_campaign=hello-elegant-code-readers http://elegantcode.com/2008/12/02/hello-elegant-code-readers/#comments Tue, 02 Dec 2008 15:18:27 +0000 Ryan Kelley http://elegantcode.com/2008/12/02/hello-elegant-code-readers/ As Jarod Ferguson already mentioned, I am now part of the Elegant Code team. I must say it is an honor to be invited to join this community and I am very excited about this opportunity. I will still cross-post on my own blog as well as here on elegantcode.com.

I am a pretty easy going guy, so hopefully this opportunity will spur me into posting with more regularity. If anybody has any topics they want me to write about just drop me a line.

One last thing, Thank You to all the Elegant Coders for giving me the invite.

]]> http://elegantcode.com/2008/12/02/hello-elegant-code-readers/feed/ 3 Joining Elegant Code http://elegantcode.com/2008/11/22/joining-elegant-code/?utm_source=rss&utm_medium=rss&utm_campaign=joining-elegant-code http://elegantcode.com/2008/11/22/joining-elegant-code/#comments Sun, 23 Nov 2008 00:52:53 +0000 Guest Blogger http://elegantcode.com/?p=1545 mentioned, i am now part of the Elegant Code team. It's an honor to be invited and i'm obviously very happy with this. All of my posts will still be posted to my own blog, as well as on elegantcode.com. And the NHibernate posts will also continue to be cross posted to NHForge. Now if you'll excuse me, i've got to start writing some posts ;)]]> http://elegantcode.com/2008/11/22/joining-elegant-code/feed/ 2 The New Blogger Toolkit http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/?utm_source=rss&utm_medium=rss&utm_campaign=quick-2008-recap-and-a-few-new-years-resolutions http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/#comments Thu, 01 Jan 2009 15:57:06 +0000 Ryan Kelley http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/ Whew, I cannot believe that 2008 is over already, it seems like it just started. 2008 was a great year for me as a developer for several reasons.

Met new People

I was able to meet a ton of new people in 2008, both online through blogs and other communities, and at KaizenConf in Austin. This is probably the single most important thing that happened to me in 2008 because it helped put me into circle of people that share the same thoughts and values about software development that I do.

Alt.Net Introduction

I was also introduced to the Alt.Net movement during 2008. I have been developing software for several years and some of the things I had been doing just didn’t seem quite right, they worked, but they had a smell to them. Enter Alt.Net, this stuff just makes sense. It is smart software development, that revolves around creating highly testable, highly maintainable code that follows the SOLID design principles. I have come to realize that if you just ask yourself “How does this proposed solution adhere to the SOLID principles” you will write much more elegant code.

KaizenConf Open Spaces Conference

This was my first open spaces conference and I didn’t know what to expect but I came away with the feeling that this was the best conference I had ever been to. KaizenConf helped fuel my fire for continuing with more Alt.Net stuff, working on Lean Software Development and KanBan methods, and staying involved with the community. It even spurred me to start blogging more frequently about these topics.

Some 2009 Resolutions

I have a few resolutions I am going to make for the new year, some are computer related, some are not.

  • Blog More – I am targeting 52 blog posts in 2009, that is a little more than double from 2008 and is only 1 per week.
  • Fish more, I love fly fishing, just need to make more time
    • Fly Fish for Bass – talk about fun!
  • Write Elegant Code – I am staying committed to SOLID principles, testability and maintainable code.
  • Learn more about Asp.Net – Especially MVC stuff, I have been doing WinForms development for the past 4 years, so I am looking forward to this one.
  • Learn a new Programming Language – Everybody should do this every year.

I am going to stop there, I don’t want to set any unrealistic expectations for myself during the year. I think all of these are very attainable and I hope that my list has spurred some inner resolution making within you to go out and commit to something new in 2009.

]]> http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/feed/ 2 Elegant Code » Blogging http://elegantcode.com Tue, 15 May 2012 10:00:00 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 I guess an introduction is in order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/?utm_source=rss&utm_medium=rss&utm_campaign=i-guess-an-introduction-is-in-order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/#comments Sun, 15 Aug 2010 21:50:26 +0000 Andreas Håkansson http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/ Twitter or from my self-titled blog that I have been blogging on up until this point (and might continue doing, haven’t really made up my mind yet what I am going to do with it). However, my real name is Andreas Håkansson and I guess I could describe myself as a nearly 30 year old .NET developer from Sweden, with a passion for pretty much everything in the software engineering / craftsmanship department (hey, why limit yourself to one kind of cake when there’s so much to be had out there!). I am a strong advocator of Open-Source Software and I head the MEF Contrib project, a set of community contributed extensions, tools and samples for the Managed Extensibility Framework, and I have also created the Common Service Factory, a WCF extension that enabled dependency injection in services (it’s a bit dated, but it works like a charm – probably should give it some love as soon as I can find a slice of spare time in my life). Oh yeah, there’s more to me than being a code ninjah – somehow I’ve also managed to get married to my high school sweetheart (12 years since we hooked up and still going strong) and together we have two wonderful boys (3 and 1½ years old – boy do they know how to keep us busy hehe) Well I guess that’s it… now you know a bit about me, and I hope to get to know a bit more about you, the readers of Elegant Code, so please stop by my posts and drop me a line or two. See you there!]]> http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/feed/ 2 What Does Elegant Code Mean to Me? http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/?utm_source=rss&utm_medium=rss&utm_campaign=what-does-elegant-code-mean-to-me http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/#comments Fri, 09 Apr 2010 19:46:38 +0000 John Sonmez http://elegantcode.com/?p=3434 What is elegance? Simply stated. Something that is simple yet effective, delivered with grace. Being simple is not enough. Simple lacking effectiveness is just a waste of time. Simple - Not Effective Simple, but not effective is a foam hammer. You don't want your code to be like a foam hammer. If it can't do what it supposed to do the simplicity just looks like stupidity instead. Effective, but not simple is something that gets thrown away or lamented. It's a Rube Goldberg machine. Rube Goldberg Machine You don't want your code to be like a Rube Goldberg machine either.  Where people look at your code because it is such a spectacle.  You don't want someone to look at your code and immediately think they want to kill you.  Code that evokes murderous rage, tends to get blamed for anything that goes wrong in the system, even if it works perfectly. If you can build something simple and its effective, it still has to be delivered in a graceful way. Consider, the elephant harness... Simple and Effective - Not Graceful Simple?  Yes, it's a box strapped on top of an Elephant, can't get much more simple than that.  Effective?  Yes, looks to me like that elephant will get you where you need to go in that terrain.  Delivered with grace?  Hmm...  Do you want to ride around on an elephant? Even if you nail the first two, with your code, you should make sure it looks and reads good.  No one wants to ride an elephant.  I have seen more than one simple effective design get thrown away because the variables were named things like "cntr" and "banana".

Elegant Code is James Bond

Women love him, men want to be like him and he kills people with a simple sophistication. When people read your code they should think James Bond, not Booger from Revenge of the Nerds. James-Bond Vs. booger
Elegant code to me is code that reads well, does what is is supposed to do and is easy to maintain. Now that I have told you what I think elegant code is, in future posts I will talk more about how to actually write elegant code.

Side Note - Joining Elegant Code

First of all I wanted to publicly thank the other Elegant Coders for inviting me to join their community. I feel honored and esteemed to be joining such a great group of software craftsmen. I also wanted to clear up confusion for anyone who has been following my blog at http://simpleprogrammer.com.  I will still be blogging there, so don't change your RSS feeds, but in addition I will be blogging here at ElegantCode.com.  If you've come here form a link on my personal blog, I encourage you to check out the other excellent bloggers on this site and consider adding Elegant Code to your RSS feed reader.   My personal blog will contain a wider array of topics, but my content here at ElegantCode.com will be centered around the theme of writing elegant code. As always, feel free to email me at john *dot* sonmez *at* gmail.com or follow me on twitter.]]> http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/feed/ 1 Welcome Two New Elegant Coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/?utm_source=rss&utm_medium=rss&utm_campaign=welcome-two-new-elegant-coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/#comments Thu, 15 Oct 2009 19:58:17 +0000 David Starr http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/ I am happy to introduce 2 new Elegant Coders! We are excited to have their contributions to the site and look forward to their wisdom.

Kirstin Juhl

@kirstinj

We are excited to have Kirstin drop wisdom like she has been doing on her current blog: I [heart] Code. From her own bio:

I am a former engineer who writes code. I did Toyota Operating System, Kanban, and Lean in my factories a decade ago, and am fascinated by its use in software development today. You can take the girl out of the factory, but you cannot take the engineer out of the girl, and so I approach everything in life as a problem to solved or optimized. Including software development. I strive to be a craftsman.

I am a mom, and I take lessons from parenthood into my work everyday.

Jason Jarrett

@staxmanade

Jason is a big-time Silverlight maven and the developer behind StatLight, a set of unit testing tools for Silverlight. I knew he was perfect for the tribe when he said, “… and so I added automocking to Unity for Silverlight.”

Yeah. :)

Welcome all.

]]> http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/feed/ 0 FubuMVC From Scratch – Part 4 Persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/?utm_source=rss&utm_medium=rss&utm_campaign=fubumvc-from-scratch-part-4-persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/#comments Wed, 25 Mar 2009 21:22:00 +0000 Ryan Kelley http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/ Previous posts in series:

Persistence is a requirement in virtually every application that we write today, and now the time has come for us to add a persistence model to our FubuMVC app. I know I mentioned moving my samples to the FubuCart source, but I am going to go ahead and implement the persistence piece in the same project the previous articles using, FubuSample. I have also added all the code for this series to the FubuMVC-Contrib project

We will be implementing our persistence model to use NHibernate, Fluent NHibernate, Repository Pattern and UnitOfWork pattern all on top of SQL Express or standard. This will also work for sqllite and other database servers.

Class and Interfaces we have to implement:

  • ISessionSourceConfiguration
  • SQLServerSessionSourceConfiguration
  • IUnitOfWork
  • INHibernateUnitOfWork
  • NHibernateUnitOfWork
  • IRepository
  • NHibernateRepository
  • DomainEntity
  • IDomainQuery
  • FubuSamplePersistenceModel

Note: I put the first two in the list in my Core.Config namespace, and the rest in Core.Persistence

Before we start you probably want to go ahead and add the following references to your core project and Web project

FubuMVC-Persist-Ref

Let’s just work our way down the list and get these files implemented.

ISessionSourceConfiguration

public interface ISessionSourceConfiguration
{
    bool IsNewDatabase { get; }
    ISessionSource CreateSessionSource(PersistenceModel model);
}

SQLServerSessionSourceConfiguration

public class SQLServerSessionSourceConfiguration : ISessionSourceConfiguration
{
    #region Implementation of ISessionSourceConfiguration
 
    public bool IsNewDatabase
    {
        get { return false; }
    }
 
    public ISessionSource CreateSessionSource(PersistenceModel model)
    {
        var properties = GetProperties();
        var source = new SessionSource(properties, model);
 
        create_schema_if_it_does_not_already_exist(source);
 
        return source;
    }
 
    private void create_schema_if_it_does_not_already_exist(ISessionSource source)
    {
        if (IsNewDatabase) source.BuildSchema();
    }
 
    protected IDictionary<string, string> GetProperties()
    {
        MsSqlConfiguration config = MsSqlConfiguration.MsSql2005;
        config.ConnectionString.FromConnectionStringWithKey(“MYDBKEY”);
        config.ShowSql();
        config.UseOuterJoin();
 
        return config.ToProperties();
    }
    #endregion
}

A quick note here: We told SQLServerSessionSourceConfiguration to use a connection string from the app settings file (Web.Config) with a key of “MYDBKEY” This will be important later.

IUnitOfWork

public interface IUnitOfWork : IDisposable
{
    void Initialize();
    void Commit();
    void Rollback();
}

INHibernateUnitOfWork

public interface INHibernateUnitOfWork : IUnitOfWork
{
    ISession CurrentSession { get; }
}

NHibernateUnitOfWork

public class NHibernateUnitOfWork : INHibernateUnitOfWork
{
    private ITransaction _transaction;
    private bool _isDisposed;
    private readonly ISessionSource _source;
    private bool _isInitialized;
 
    public NHibernateUnitOfWork(ISessionSource source)
    {
        _source = source;
    }
 
    public void Initialize()
    {
        should_not_currently_be_disposed();
 
        CurrentSession = _source.CreateSession();
        begin_new_transaction();
 
        _isInitialized = true;
    }
 
    public ISession CurrentSession { get; private set; }
 
    public void Commit()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Commit();
 
        begin_new_transaction();
    }
 
    private void begin_new_transaction()
    {
        if (_transaction != null)
        {
            _transaction.Dispose();
        }
 
        _transaction = CurrentSession.BeginTransaction();
    }
 
    public void Rollback()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Rollback();
 
        begin_new_transaction();
    }
 
    private void should_not_currently_be_disposed()
    {
        if (_isDisposed) throw new ObjectDisposedException(GetType().Name);
    }
 
    private void should_be_initialized_first()
    {
        if (!_isInitialized) throw new InvalidOperationException("Must initialize (call Initialize()) on NHibernateUnitOfWork before commiting or rolling back");
    }
 
    public void Dispose()
    {
        if (_isDisposed || !_isInitialized) return;
 
        _transaction.Dispose();
        CurrentSession.Dispose();
 
        _isDisposed = true;
    }
}

IRepository

public interface IRepository
{
    void Save<ENTITY>(ENTITY entity)
        where ENTITY : DomainEntity;
 
    ENTITY Load<ENTITY>(Guid id)
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>()
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery)
        where ENTITY : DomainEntity;
 
    void Delete<ENTITY>(ENTITY entity);
 
    void DeleteAll<ENTITY>();
}

NHibernateRepository

public class NHibernateRepository : IRepository
{
    private readonly INHibernateUnitOfWork _unitOfWork;
 
    public NHibernateRepository(INHibernateUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public void Save<ENTITY>(ENTITY entity) where ENTITY : DomainEntity
    {
        _unitOfWork.CurrentSession.SaveOrUpdate(entity);
    }
 
    public ENTITY Load<ENTITY>(Guid id) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Load<ENTITY>(id);
    }
 
    public IQueryable<ENTITY> Query<ENTITY>() where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>();
    }
 
    public IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>().Where(whereQuery.Expression);
    }
 
    public void Delete<ENTITY>(ENTITY entity)
    {
        _unitOfWork.CurrentSession.Delete(entity);   
    }
 
    public void DeleteAll<ENTITY>()
    {
        var query = String.Format("from {0}", typeof(ENTITY).Name);
        _unitOfWork.CurrentSession.Delete(query);   
    }
}

DomainEntity

Note: I put both of these classes in my Core.Domain namespace, also XML comments are in Source Repository

public class DomainEntity : IEquatable<DomainEntity>
{
    public virtual Guid ID { get; set; }
 
    public virtual bool Equals(DomainEntity other)
    {
        if (ReferenceEquals(null, other)) return false;
        if (ReferenceEquals(this, other)) return true;
        return other.ID.Equals(ID);
    }
 
    public override bool Equals(object obj)
    {
        if (ReferenceEquals(null, obj)) return false;
        if (ReferenceEquals(this, obj)) return true;
        if (obj.GetType() != GetType()) return false;
        return Equals((DomainEntity)obj);
    }
 
    public override int GetHashCode()
    {
        return ID.GetHashCode();
    }
 
    public static bool operator ==(DomainEntity left, DomainEntity right)
    {
        return Equals(left, right);
    }
 
    public static bool operator !=(DomainEntity left, DomainEntity right)
    {
        return !Equals(left, right);
    }
}

IDomainQuery

public interface IDomainQuery<ENTITY>
    where ENTITY : DomainEntity
{
    Expression<Func<ENTITY, bool>> Expression { get; }
}

FubuSamplePersistenceModel

namespace FubuSample.Core.Domain.Persistence
{
    public class FubuSamplePersistenceModel : PersistenceModel
    {
        public FubuSamplePersistenceModel()
        {
            addMappingsFromThisAssembly();
        }
    }
}

Now that we have all the puzzle pieces in place we need to hook them up and make them do some work. Open up FubuSampleWebRegistry

And add the following code:

protected override void configure()
{
    ForRequestedType<ISessionSourceConfiguration>().AsSingletons()
        .TheDefault.Is.OfConcreteType<SQLServerSessionSourceConfiguration>();
 
 
    ForRequestedType<ISessionSource>().AsSingletons()
        .TheDefault.Is.ConstructedBy(ctx =>
                                     ctx.GetInstance<ISessionSourceConfiguration>()
                                         .CreateSessionSource(new FubuSamplePersistenceModel()));
 
    ForRequestedType<IUnitOfWork>().TheDefault.Is.ConstructedBy(ctx => ctx.GetInstance<INHibernateUnitOfWork>());
 
    ForRequestedType<INHibernateUnitOfWork>().CacheBy(InstanceScope.Hybrid)
        .TheDefault.Is.OfConcreteType<NHibernateUnitOfWork>();
 
    ForRequestedType<IRepository>().TheDefault.Is.OfConcreteType<NHibernateRepository>();
}

With a little luck and all of our mad skills, we should be able to talk to the database now. So we need to plumb our simple product object up to talk to NHibernate. We will do this with a mapping file, and since we are using FluentNHibernate we can do this strongly typed.

Make the following modifications to Product: Extend DomainEntity and get rid of Id Property, it is inherited

public class Product : DomainEntity
{
    public virtual string Name { get; set; }
    public virtual string Description { get; set; }
}

Add mapping file for Product:

namespace FubuSample.Core.Domain.Mapping
{
    public class ProductMap : ClassMap<Product>
    {
        public ProductMap()
        {
            Id(e => e.ID).GeneratedBy.GuidComb();
 
            Map(p => p.Name);
            Map(p => p.Description);
            
        }
    }
}

You may also want to setup your connection string at this point in the Web.Config file, mine looks like this:

<add name="MYDBKEY" connectionString="Data Source=LOCALHOST;initial catalog=FubuSample;Integrated Security=SSPI;" providerName="System.Data.SqlClient" />

I also created an empty database in my local SQL Server instance called “FubuSample” And then I went back to SQLServerSessionSourceConfiguration and changed the value of IsNewDatabase to return true. This will create the schema for the database when the application first runs. There is a multitude of different ways that we can handle this, but this was easy for the tutorial purposes.

Next we will add a behavior to our core project and tell FubuMVC to apply that behavior to all or our ControllerActions.

Create a class named “access_the_database_through_a_unit_of_work” in your Core.Web.Behaviors namespace. The contents will look like this:

public class access_the_database_through_a_unit_of_work : IControllerActionBehavior
{
    private readonly IUnitOfWork _unitOfWork;
 
    public access_the_database_through_a_unit_of_work(IUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public IControllerActionBehavior InsideBehavior { get; set; }
    public IInvocationResult Result { get; set; }
 
    public OUTPUT Invoke<INPUT, OUTPUT>(INPUT input, Func<INPUT, OUTPUT> func)
        where INPUT : class
        where OUTPUT : class
    {
        _unitOfWork.Initialize();
 
        try
        {
            var output = InsideBehavior.Invoke(input, func);
            Result = InsideBehavior.Result;
 
            _unitOfWork.Commit();
 
            return output;
        }
        catch
        {
            _unitOfWork.Rollback();
            throw;
        }
        finally
        {
            _unitOfWork.Dispose();
        }
    }
}

Now to tell FubuMVC what to do, open up Global.asax.cs or your Bootstrapper, wherever you are doing the configuration of FubuMVC. In this project we are doing it in Global.asax.cs Add a new behavior to the section that starts with “x.ByDefault.EveryControllerAction” so it looks like this:

x.ByDefault.EveryControllerAction(d =>
   {
       d.Will<execute_the_result>();
       d.Will<access_the_database_through_a_unit_of_work>();
   });

The last thing we will do is open up HomeController and add this code above the Index action:

private IRepository _repository;
 
public HomeController(IRepository repository)
{
    _repository = repository;
}

I also modified the Index action to go ahead and create some database values before we query for them just so we can test this thing. (I only did this for the tutorial, I swear) So modify the Index action to look like this:

public IndexViewModel Index(IndexSetupViewModel inModel)
{
    var prod1 = new Product {Name = "TestProduct1", Description = "This is a test product"};
 
    _repository.Save(prod1);
 
    var prod2 = new Product {Name = "TestProduct2", Description = "This is a test product"};
 
    _repository.Save(prod2);
 
    var outModel = new IndexViewModel();
 
    var productList = _repository.Query<Product>();
 
    outModel.Products = productList.ToList().Select(x => new ProductDisplay(x));
 
    return outModel;
}

Now with you should be able to run your web app and browse to /home and all this will be executed and you will be on your way to creating a whole bunch of persist able objects for use with your FubuMVC app.

As always, feedback is welcome.

]]> http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/feed/ 9 It’s Official – New Gig started last week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/?utm_source=rss&utm_medium=rss&utm_campaign=its-official-new-gig-started-last-week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/#comments Tue, 24 Feb 2009 19:03:21 +0000 Ryan Kelley http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/ CoachesAid.com. CoachesAid is a High School sports website that is expanding rapidly and it is my task to make this expansion happen as smoothly and as quickly as possible. The past month has been very hectic as I was wrapping up loose ends at my previous engagement. I started my new gig last week, but I have pretty much been building furniture and getting computer and server ready to go. The next few weeks will also be challenging as I start to assemble the team of people that is going to make this all happen. How does this tie into the practice of Elegant Coding? Funny you should ask that, the current infrastructure they are built on is a maintenance nightmare so project number one is to completely redo their entire site infrastructure in ASP.Net, and yes it will be MVC based, but not ASP.Net MVC. I am going to architect and build their new infrastructure from the ground up on FubuMVC. So expect a lot more posts from me on FubuMVC and I may even have questions for you dear reader. Side Note: I just finished deploying to production a small scale site built on FubuMVC, and it ROCKS! There is going to be some stuff that needs to be tweaked out and added to the core, but overall, fully functional MVC framework. I hope I haven’t bored you with too much personal information, but I have to go. (I have several FubuMVC posts stacked up in my queue) -Ryan]]> http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/feed/ 8 Quick 2008 Recap and a few New Years Resolutions http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/?utm_source=rss&utm_medium=rss&utm_campaign=quick-2008-recap-and-a-few-new-years-resolutions http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/#comments Thu, 01 Jan 2009 15:57:06 +0000 Ryan Kelley http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/ Whew, I cannot believe that 2008 is over already, it seems like it just started. 2008 was a great year for me as a developer for several reasons.

Met new People

I was able to meet a ton of new people in 2008, both online through blogs and other communities, and at KaizenConf in Austin. This is probably the single most important thing that happened to me in 2008 because it helped put me into circle of people that share the same thoughts and values about software development that I do.

Alt.Net Introduction

I was also introduced to the Alt.Net movement during 2008. I have been developing software for several years and some of the things I had been doing just didn’t seem quite right, they worked, but they had a smell to them. Enter Alt.Net, this stuff just makes sense. It is smart software development, that revolves around creating highly testable, highly maintainable code that follows the SOLID design principles. I have come to realize that if you just ask yourself “How does this proposed solution adhere to the SOLID principles” you will write much more elegant code.

KaizenConf Open Spaces Conference

This was my first open spaces conference and I didn’t know what to expect but I came away with the feeling that this was the best conference I had ever been to. KaizenConf helped fuel my fire for continuing with more Alt.Net stuff, working on Lean Software Development and KanBan methods, and staying involved with the community. It even spurred me to start blogging more frequently about these topics.

Some 2009 Resolutions

I have a few resolutions I am going to make for the new year, some are computer related, some are not.

  • Blog More – I am targeting 52 blog posts in 2009, that is a little more than double from 2008 and is only 1 per week.
  • Fish more, I love fly fishing, just need to make more time
    • Fly Fish for Bass – talk about fun!
  • Write Elegant Code – I am staying committed to SOLID principles, testability and maintainable code.
  • Learn more about Asp.Net – Especially MVC stuff, I have been doing WinForms development for the past 4 years, so I am looking forward to this one.
  • Learn a new Programming Language – Everybody should do this every year.

I am going to stop there, I don’t want to set any unrealistic expectations for myself during the year. I think all of these are very attainable and I hope that my list has spurred some inner resolution making within you to go out and commit to something new in 2009.

]]> http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/feed/ 2 Hello Elegant Code Readers http://elegantcode.com/2008/12/02/hello-elegant-code-readers/?utm_source=rss&utm_medium=rss&utm_campaign=hello-elegant-code-readers http://elegantcode.com/2008/12/02/hello-elegant-code-readers/#comments Tue, 02 Dec 2008 15:18:27 +0000 Ryan Kelley http://elegantcode.com/2008/12/02/hello-elegant-code-readers/ As Jarod Ferguson already mentioned, I am now part of the Elegant Code team. I must say it is an honor to be invited to join this community and I am very excited about this opportunity. I will still cross-post on my own blog as well as here on elegantcode.com.

I am a pretty easy going guy, so hopefully this opportunity will spur me into posting with more regularity. If anybody has any topics they want me to write about just drop me a line.

One last thing, Thank You to all the Elegant Coders for giving me the invite.

]]> http://elegantcode.com/2008/12/02/hello-elegant-code-readers/feed/ 3 Joining Elegant Code http://elegantcode.com/2008/11/22/joining-elegant-code/?utm_source=rss&utm_medium=rss&utm_campaign=joining-elegant-code http://elegantcode.com/2008/11/22/joining-elegant-code/#comments Sun, 23 Nov 2008 00:52:53 +0000 Guest Blogger http://elegantcode.com/?p=1545 mentioned, i am now part of the Elegant Code team. It's an honor to be invited and i'm obviously very happy with this. All of my posts will still be posted to my own blog, as well as on elegantcode.com. And the NHibernate posts will also continue to be cross posted to NHForge. Now if you'll excuse me, i've got to start writing some posts ;)]]> http://elegantcode.com/2008/11/22/joining-elegant-code/feed/ 2 The New Blogger Toolkit http://elegantcode.com/2008/12/02/hello-elegant-code-readers/?utm_source=rss&utm_medium=rss&utm_campaign=hello-elegant-code-readers http://elegantcode.com/2008/12/02/hello-elegant-code-readers/#comments Tue, 02 Dec 2008 15:18:27 +0000 Ryan Kelley http://elegantcode.com/2008/12/02/hello-elegant-code-readers/ As Jarod Ferguson already mentioned, I am now part of the Elegant Code team. I must say it is an honor to be invited to join this community and I am very excited about this opportunity. I will still cross-post on my own blog as well as here on elegantcode.com.

I am a pretty easy going guy, so hopefully this opportunity will spur me into posting with more regularity. If anybody has any topics they want me to write about just drop me a line.

One last thing, Thank You to all the Elegant Coders for giving me the invite.

]]> http://elegantcode.com/2008/12/02/hello-elegant-code-readers/feed/ 3 Elegant Code » Blogging http://elegantcode.com Tue, 15 May 2012 10:00:00 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 I guess an introduction is in order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/?utm_source=rss&utm_medium=rss&utm_campaign=i-guess-an-introduction-is-in-order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/#comments Sun, 15 Aug 2010 21:50:26 +0000 Andreas Håkansson http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/ Twitter or from my self-titled blog that I have been blogging on up until this point (and might continue doing, haven’t really made up my mind yet what I am going to do with it). However, my real name is Andreas Håkansson and I guess I could describe myself as a nearly 30 year old .NET developer from Sweden, with a passion for pretty much everything in the software engineering / craftsmanship department (hey, why limit yourself to one kind of cake when there’s so much to be had out there!). I am a strong advocator of Open-Source Software and I head the MEF Contrib project, a set of community contributed extensions, tools and samples for the Managed Extensibility Framework, and I have also created the Common Service Factory, a WCF extension that enabled dependency injection in services (it’s a bit dated, but it works like a charm – probably should give it some love as soon as I can find a slice of spare time in my life). Oh yeah, there’s more to me than being a code ninjah – somehow I’ve also managed to get married to my high school sweetheart (12 years since we hooked up and still going strong) and together we have two wonderful boys (3 and 1½ years old – boy do they know how to keep us busy hehe) Well I guess that’s it… now you know a bit about me, and I hope to get to know a bit more about you, the readers of Elegant Code, so please stop by my posts and drop me a line or two. See you there!]]> http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/feed/ 2 What Does Elegant Code Mean to Me? http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/?utm_source=rss&utm_medium=rss&utm_campaign=what-does-elegant-code-mean-to-me http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/#comments Fri, 09 Apr 2010 19:46:38 +0000 John Sonmez http://elegantcode.com/?p=3434 What is elegance? Simply stated. Something that is simple yet effective, delivered with grace. Being simple is not enough. Simple lacking effectiveness is just a waste of time. Simple - Not Effective Simple, but not effective is a foam hammer. You don't want your code to be like a foam hammer. If it can't do what it supposed to do the simplicity just looks like stupidity instead. Effective, but not simple is something that gets thrown away or lamented. It's a Rube Goldberg machine. Rube Goldberg Machine You don't want your code to be like a Rube Goldberg machine either.  Where people look at your code because it is such a spectacle.  You don't want someone to look at your code and immediately think they want to kill you.  Code that evokes murderous rage, tends to get blamed for anything that goes wrong in the system, even if it works perfectly. If you can build something simple and its effective, it still has to be delivered in a graceful way. Consider, the elephant harness... Simple and Effective - Not Graceful Simple?  Yes, it's a box strapped on top of an Elephant, can't get much more simple than that.  Effective?  Yes, looks to me like that elephant will get you where you need to go in that terrain.  Delivered with grace?  Hmm...  Do you want to ride around on an elephant? Even if you nail the first two, with your code, you should make sure it looks and reads good.  No one wants to ride an elephant.  I have seen more than one simple effective design get thrown away because the variables were named things like "cntr" and "banana".

Elegant Code is James Bond

Women love him, men want to be like him and he kills people with a simple sophistication. When people read your code they should think James Bond, not Booger from Revenge of the Nerds. James-Bond Vs. booger
Elegant code to me is code that reads well, does what is is supposed to do and is easy to maintain. Now that I have told you what I think elegant code is, in future posts I will talk more about how to actually write elegant code.

Side Note - Joining Elegant Code

First of all I wanted to publicly thank the other Elegant Coders for inviting me to join their community. I feel honored and esteemed to be joining such a great group of software craftsmen. I also wanted to clear up confusion for anyone who has been following my blog at http://simpleprogrammer.com.  I will still be blogging there, so don't change your RSS feeds, but in addition I will be blogging here at ElegantCode.com.  If you've come here form a link on my personal blog, I encourage you to check out the other excellent bloggers on this site and consider adding Elegant Code to your RSS feed reader.   My personal blog will contain a wider array of topics, but my content here at ElegantCode.com will be centered around the theme of writing elegant code. As always, feel free to email me at john *dot* sonmez *at* gmail.com or follow me on twitter.]]> http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/feed/ 1 Welcome Two New Elegant Coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/?utm_source=rss&utm_medium=rss&utm_campaign=welcome-two-new-elegant-coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/#comments Thu, 15 Oct 2009 19:58:17 +0000 David Starr http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/ I am happy to introduce 2 new Elegant Coders! We are excited to have their contributions to the site and look forward to their wisdom.

Kirstin Juhl

@kirstinj

We are excited to have Kirstin drop wisdom like she has been doing on her current blog: I [heart] Code. From her own bio:

I am a former engineer who writes code. I did Toyota Operating System, Kanban, and Lean in my factories a decade ago, and am fascinated by its use in software development today. You can take the girl out of the factory, but you cannot take the engineer out of the girl, and so I approach everything in life as a problem to solved or optimized. Including software development. I strive to be a craftsman.

I am a mom, and I take lessons from parenthood into my work everyday.

Jason Jarrett

@staxmanade

Jason is a big-time Silverlight maven and the developer behind StatLight, a set of unit testing tools for Silverlight. I knew he was perfect for the tribe when he said, “… and so I added automocking to Unity for Silverlight.”

Yeah. :)

Welcome all.

]]> http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/feed/ 0 FubuMVC From Scratch – Part 4 Persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/?utm_source=rss&utm_medium=rss&utm_campaign=fubumvc-from-scratch-part-4-persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/#comments Wed, 25 Mar 2009 21:22:00 +0000 Ryan Kelley http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/ Previous posts in series:

Persistence is a requirement in virtually every application that we write today, and now the time has come for us to add a persistence model to our FubuMVC app. I know I mentioned moving my samples to the FubuCart source, but I am going to go ahead and implement the persistence piece in the same project the previous articles using, FubuSample. I have also added all the code for this series to the FubuMVC-Contrib project

We will be implementing our persistence model to use NHibernate, Fluent NHibernate, Repository Pattern and UnitOfWork pattern all on top of SQL Express or standard. This will also work for sqllite and other database servers.

Class and Interfaces we have to implement:

  • ISessionSourceConfiguration
  • SQLServerSessionSourceConfiguration
  • IUnitOfWork
  • INHibernateUnitOfWork
  • NHibernateUnitOfWork
  • IRepository
  • NHibernateRepository
  • DomainEntity
  • IDomainQuery
  • FubuSamplePersistenceModel

Note: I put the first two in the list in my Core.Config namespace, and the rest in Core.Persistence

Before we start you probably want to go ahead and add the following references to your core project and Web project

FubuMVC-Persist-Ref

Let’s just work our way down the list and get these files implemented.

ISessionSourceConfiguration

public interface ISessionSourceConfiguration
{
    bool IsNewDatabase { get; }
    ISessionSource CreateSessionSource(PersistenceModel model);
}

SQLServerSessionSourceConfiguration

public class SQLServerSessionSourceConfiguration : ISessionSourceConfiguration
{
    #region Implementation of ISessionSourceConfiguration
 
    public bool IsNewDatabase
    {
        get { return false; }
    }
 
    public ISessionSource CreateSessionSource(PersistenceModel model)
    {
        var properties = GetProperties();
        var source = new SessionSource(properties, model);
 
        create_schema_if_it_does_not_already_exist(source);
 
        return source;
    }
 
    private void create_schema_if_it_does_not_already_exist(ISessionSource source)
    {
        if (IsNewDatabase) source.BuildSchema();
    }
 
    protected IDictionary<string, string> GetProperties()
    {
        MsSqlConfiguration config = MsSqlConfiguration.MsSql2005;
        config.ConnectionString.FromConnectionStringWithKey(“MYDBKEY”);
        config.ShowSql();
        config.UseOuterJoin();
 
        return config.ToProperties();
    }
    #endregion
}

A quick note here: We told SQLServerSessionSourceConfiguration to use a connection string from the app settings file (Web.Config) with a key of “MYDBKEY” This will be important later.

IUnitOfWork

public interface IUnitOfWork : IDisposable
{
    void Initialize();
    void Commit();
    void Rollback();
}

INHibernateUnitOfWork

public interface INHibernateUnitOfWork : IUnitOfWork
{
    ISession CurrentSession { get; }
}

NHibernateUnitOfWork

public class NHibernateUnitOfWork : INHibernateUnitOfWork
{
    private ITransaction _transaction;
    private bool _isDisposed;
    private readonly ISessionSource _source;
    private bool _isInitialized;
 
    public NHibernateUnitOfWork(ISessionSource source)
    {
        _source = source;
    }
 
    public void Initialize()
    {
        should_not_currently_be_disposed();
 
        CurrentSession = _source.CreateSession();
        begin_new_transaction();
 
        _isInitialized = true;
    }
 
    public ISession CurrentSession { get; private set; }
 
    public void Commit()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Commit();
 
        begin_new_transaction();
    }
 
    private void begin_new_transaction()
    {
        if (_transaction != null)
        {
            _transaction.Dispose();
        }
 
        _transaction = CurrentSession.BeginTransaction();
    }
 
    public void Rollback()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Rollback();
 
        begin_new_transaction();
    }
 
    private void should_not_currently_be_disposed()
    {
        if (_isDisposed) throw new ObjectDisposedException(GetType().Name);
    }
 
    private void should_be_initialized_first()
    {
        if (!_isInitialized) throw new InvalidOperationException("Must initialize (call Initialize()) on NHibernateUnitOfWork before commiting or rolling back");
    }
 
    public void Dispose()
    {
        if (_isDisposed || !_isInitialized) return;
 
        _transaction.Dispose();
        CurrentSession.Dispose();
 
        _isDisposed = true;
    }
}

IRepository

public interface IRepository
{
    void Save<ENTITY>(ENTITY entity)
        where ENTITY : DomainEntity;
 
    ENTITY Load<ENTITY>(Guid id)
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>()
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery)
        where ENTITY : DomainEntity;
 
    void Delete<ENTITY>(ENTITY entity);
 
    void DeleteAll<ENTITY>();
}

NHibernateRepository

public class NHibernateRepository : IRepository
{
    private readonly INHibernateUnitOfWork _unitOfWork;
 
    public NHibernateRepository(INHibernateUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public void Save<ENTITY>(ENTITY entity) where ENTITY : DomainEntity
    {
        _unitOfWork.CurrentSession.SaveOrUpdate(entity);
    }
 
    public ENTITY Load<ENTITY>(Guid id) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Load<ENTITY>(id);
    }
 
    public IQueryable<ENTITY> Query<ENTITY>() where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>();
    }
 
    public IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>().Where(whereQuery.Expression);
    }
 
    public void Delete<ENTITY>(ENTITY entity)
    {
        _unitOfWork.CurrentSession.Delete(entity);   
    }
 
    public void DeleteAll<ENTITY>()
    {
        var query = String.Format("from {0}", typeof(ENTITY).Name);
        _unitOfWork.CurrentSession.Delete(query);   
    }
}

DomainEntity

Note: I put both of these classes in my Core.Domain namespace, also XML comments are in Source Repository

public class DomainEntity : IEquatable<DomainEntity>
{
    public virtual Guid ID { get; set; }
 
    public virtual bool Equals(DomainEntity other)
    {
        if (ReferenceEquals(null, other)) return false;
        if (ReferenceEquals(this, other)) return true;
        return other.ID.Equals(ID);
    }
 
    public override bool Equals(object obj)
    {
        if (ReferenceEquals(null, obj)) return false;
        if (ReferenceEquals(this, obj)) return true;
        if (obj.GetType() != GetType()) return false;
        return Equals((DomainEntity)obj);
    }
 
    public override int GetHashCode()
    {
        return ID.GetHashCode();
    }
 
    public static bool operator ==(DomainEntity left, DomainEntity right)
    {
        return Equals(left, right);
    }
 
    public static bool operator !=(DomainEntity left, DomainEntity right)
    {
        return !Equals(left, right);
    }
}

IDomainQuery

public interface IDomainQuery<ENTITY>
    where ENTITY : DomainEntity
{
    Expression<Func<ENTITY, bool>> Expression { get; }
}

FubuSamplePersistenceModel

namespace FubuSample.Core.Domain.Persistence
{
    public class FubuSamplePersistenceModel : PersistenceModel
    {
        public FubuSamplePersistenceModel()
        {
            addMappingsFromThisAssembly();
        }
    }
}

Now that we have all the puzzle pieces in place we need to hook them up and make them do some work. Open up FubuSampleWebRegistry

And add the following code:

protected override void configure()
{
    ForRequestedType<ISessionSourceConfiguration>().AsSingletons()
        .TheDefault.Is.OfConcreteType<SQLServerSessionSourceConfiguration>();
 
 
    ForRequestedType<ISessionSource>().AsSingletons()
        .TheDefault.Is.ConstructedBy(ctx =>
                                     ctx.GetInstance<ISessionSourceConfiguration>()
                                         .CreateSessionSource(new FubuSamplePersistenceModel()));
 
    ForRequestedType<IUnitOfWork>().TheDefault.Is.ConstructedBy(ctx => ctx.GetInstance<INHibernateUnitOfWork>());
 
    ForRequestedType<INHibernateUnitOfWork>().CacheBy(InstanceScope.Hybrid)
        .TheDefault.Is.OfConcreteType<NHibernateUnitOfWork>();
 
    ForRequestedType<IRepository>().TheDefault.Is.OfConcreteType<NHibernateRepository>();
}

With a little luck and all of our mad skills, we should be able to talk to the database now. So we need to plumb our simple product object up to talk to NHibernate. We will do this with a mapping file, and since we are using FluentNHibernate we can do this strongly typed.

Make the following modifications to Product: Extend DomainEntity and get rid of Id Property, it is inherited

public class Product : DomainEntity
{
    public virtual string Name { get; set; }
    public virtual string Description { get; set; }
}

Add mapping file for Product:

namespace FubuSample.Core.Domain.Mapping
{
    public class ProductMap : ClassMap<Product>
    {
        public ProductMap()
        {
            Id(e => e.ID).GeneratedBy.GuidComb();
 
            Map(p => p.Name);
            Map(p => p.Description);
            
        }
    }
}

You may also want to setup your connection string at this point in the Web.Config file, mine looks like this:

<add name="MYDBKEY" connectionString="Data Source=LOCALHOST;initial catalog=FubuSample;Integrated Security=SSPI;" providerName="System.Data.SqlClient" />

I also created an empty database in my local SQL Server instance called “FubuSample” And then I went back to SQLServerSessionSourceConfiguration and changed the value of IsNewDatabase to return true. This will create the schema for the database when the application first runs. There is a multitude of different ways that we can handle this, but this was easy for the tutorial purposes.

Next we will add a behavior to our core project and tell FubuMVC to apply that behavior to all or our ControllerActions.

Create a class named “access_the_database_through_a_unit_of_work” in your Core.Web.Behaviors namespace. The contents will look like this:

public class access_the_database_through_a_unit_of_work : IControllerActionBehavior
{
    private readonly IUnitOfWork _unitOfWork;
 
    public access_the_database_through_a_unit_of_work(IUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public IControllerActionBehavior InsideBehavior { get; set; }
    public IInvocationResult Result { get; set; }
 
    public OUTPUT Invoke<INPUT, OUTPUT>(INPUT input, Func<INPUT, OUTPUT> func)
        where INPUT : class
        where OUTPUT : class
    {
        _unitOfWork.Initialize();
 
        try
        {
            var output = InsideBehavior.Invoke(input, func);
            Result = InsideBehavior.Result;
 
            _unitOfWork.Commit();
 
            return output;
        }
        catch
        {
            _unitOfWork.Rollback();
            throw;
        }
        finally
        {
            _unitOfWork.Dispose();
        }
    }
}

Now to tell FubuMVC what to do, open up Global.asax.cs or your Bootstrapper, wherever you are doing the configuration of FubuMVC. In this project we are doing it in Global.asax.cs Add a new behavior to the section that starts with “x.ByDefault.EveryControllerAction” so it looks like this:

x.ByDefault.EveryControllerAction(d =>
   {
       d.Will<execute_the_result>();
       d.Will<access_the_database_through_a_unit_of_work>();
   });

The last thing we will do is open up HomeController and add this code above the Index action:

private IRepository _repository;
 
public HomeController(IRepository repository)
{
    _repository = repository;
}

I also modified the Index action to go ahead and create some database values before we query for them just so we can test this thing. (I only did this for the tutorial, I swear) So modify the Index action to look like this:

public IndexViewModel Index(IndexSetupViewModel inModel)
{
    var prod1 = new Product {Name = "TestProduct1", Description = "This is a test product"};
 
    _repository.Save(prod1);
 
    var prod2 = new Product {Name = "TestProduct2", Description = "This is a test product"};
 
    _repository.Save(prod2);
 
    var outModel = new IndexViewModel();
 
    var productList = _repository.Query<Product>();
 
    outModel.Products = productList.ToList().Select(x => new ProductDisplay(x));
 
    return outModel;
}

Now with you should be able to run your web app and browse to /home and all this will be executed and you will be on your way to creating a whole bunch of persist able objects for use with your FubuMVC app.

As always, feedback is welcome.

]]> http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/feed/ 9 It’s Official – New Gig started last week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/?utm_source=rss&utm_medium=rss&utm_campaign=its-official-new-gig-started-last-week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/#comments Tue, 24 Feb 2009 19:03:21 +0000 Ryan Kelley http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/ CoachesAid.com. CoachesAid is a High School sports website that is expanding rapidly and it is my task to make this expansion happen as smoothly and as quickly as possible. The past month has been very hectic as I was wrapping up loose ends at my previous engagement. I started my new gig last week, but I have pretty much been building furniture and getting computer and server ready to go. The next few weeks will also be challenging as I start to assemble the team of people that is going to make this all happen. How does this tie into the practice of Elegant Coding? Funny you should ask that, the current infrastructure they are built on is a maintenance nightmare so project number one is to completely redo their entire site infrastructure in ASP.Net, and yes it will be MVC based, but not ASP.Net MVC. I am going to architect and build their new infrastructure from the ground up on FubuMVC. So expect a lot more posts from me on FubuMVC and I may even have questions for you dear reader. Side Note: I just finished deploying to production a small scale site built on FubuMVC, and it ROCKS! There is going to be some stuff that needs to be tweaked out and added to the core, but overall, fully functional MVC framework. I hope I haven’t bored you with too much personal information, but I have to go. (I have several FubuMVC posts stacked up in my queue) -Ryan]]> http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/feed/ 8 Quick 2008 Recap and a few New Years Resolutions http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/?utm_source=rss&utm_medium=rss&utm_campaign=quick-2008-recap-and-a-few-new-years-resolutions http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/#comments Thu, 01 Jan 2009 15:57:06 +0000 Ryan Kelley http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/ Whew, I cannot believe that 2008 is over already, it seems like it just started. 2008 was a great year for me as a developer for several reasons.

Met new People

I was able to meet a ton of new people in 2008, both online through blogs and other communities, and at KaizenConf in Austin. This is probably the single most important thing that happened to me in 2008 because it helped put me into circle of people that share the same thoughts and values about software development that I do.

Alt.Net Introduction

I was also introduced to the Alt.Net movement during 2008. I have been developing software for several years and some of the things I had been doing just didn’t seem quite right, they worked, but they had a smell to them. Enter Alt.Net, this stuff just makes sense. It is smart software development, that revolves around creating highly testable, highly maintainable code that follows the SOLID design principles. I have come to realize that if you just ask yourself “How does this proposed solution adhere to the SOLID principles” you will write much more elegant code.

KaizenConf Open Spaces Conference

This was my first open spaces conference and I didn’t know what to expect but I came away with the feeling that this was the best conference I had ever been to. KaizenConf helped fuel my fire for continuing with more Alt.Net stuff, working on Lean Software Development and KanBan methods, and staying involved with the community. It even spurred me to start blogging more frequently about these topics.

Some 2009 Resolutions

I have a few resolutions I am going to make for the new year, some are computer related, some are not.

  • Blog More – I am targeting 52 blog posts in 2009, that is a little more than double from 2008 and is only 1 per week.
  • Fish more, I love fly fishing, just need to make more time
    • Fly Fish for Bass – talk about fun!
  • Write Elegant Code – I am staying committed to SOLID principles, testability and maintainable code.
  • Learn more about Asp.Net – Especially MVC stuff, I have been doing WinForms development for the past 4 years, so I am looking forward to this one.
  • Learn a new Programming Language – Everybody should do this every year.

I am going to stop there, I don’t want to set any unrealistic expectations for myself during the year. I think all of these are very attainable and I hope that my list has spurred some inner resolution making within you to go out and commit to something new in 2009.

]]> http://elegantcode.com/2009/01/01/quick-2008-recap-and-a-few-new-years-resolutions/feed/ 2 Hello Elegant Code Readers http://elegantcode.com/2008/12/02/hello-elegant-code-readers/?utm_source=rss&utm_medium=rss&utm_campaign=hello-elegant-code-readers http://elegantcode.com/2008/12/02/hello-elegant-code-readers/#comments Tue, 02 Dec 2008 15:18:27 +0000 Ryan Kelley http://elegantcode.com/2008/12/02/hello-elegant-code-readers/ As Jarod Ferguson already mentioned, I am now part of the Elegant Code team. I must say it is an honor to be invited to join this community and I am very excited about this opportunity. I will still cross-post on my own blog as well as here on elegantcode.com.

I am a pretty easy going guy, so hopefully this opportunity will spur me into posting with more regularity. If anybody has any topics they want me to write about just drop me a line.

One last thing, Thank You to all the Elegant Coders for giving me the invite.

]]> http://elegantcode.com/2008/12/02/hello-elegant-code-readers/feed/ 3 Joining Elegant Code http://elegantcode.com/2008/11/22/joining-elegant-code/?utm_source=rss&utm_medium=rss&utm_campaign=joining-elegant-code http://elegantcode.com/2008/11/22/joining-elegant-code/#comments Sun, 23 Nov 2008 00:52:53 +0000 Guest Blogger http://elegantcode.com/?p=1545 mentioned, i am now part of the Elegant Code team. It's an honor to be invited and i'm obviously very happy with this. All of my posts will still be posted to my own blog, as well as on elegantcode.com. And the NHibernate posts will also continue to be cross posted to NHForge. Now if you'll excuse me, i've got to start writing some posts ;)]]> http://elegantcode.com/2008/11/22/joining-elegant-code/feed/ 2 The New Blogger Toolkit http://elegantcode.com/2008/11/22/joining-elegant-code/?utm_source=rss&utm_medium=rss&utm_campaign=joining-elegant-code http://elegantcode.com/2008/11/22/joining-elegant-code/#comments Sun, 23 Nov 2008 00:52:53 +0000 Guest Blogger http://elegantcode.com/?p=1545 mentioned, i am now part of the Elegant Code team. It's an honor to be invited and i'm obviously very happy with this. All of my posts will still be posted to my own blog, as well as on elegantcode.com. And the NHibernate posts will also continue to be cross posted to NHForge. Now if you'll excuse me, i've got to start writing some posts ;)]]> http://elegantcode.com/2008/11/22/joining-elegant-code/feed/ 2 Elegant Code » Blogging http://elegantcode.com Tue, 15 May 2012 10:00:00 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 I guess an introduction is in order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/?utm_source=rss&utm_medium=rss&utm_campaign=i-guess-an-introduction-is-in-order http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/#comments Sun, 15 Aug 2010 21:50:26 +0000 Andreas Håkansson http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/ Twitter or from my self-titled blog that I have been blogging on up until this point (and might continue doing, haven’t really made up my mind yet what I am going to do with it). However, my real name is Andreas Håkansson and I guess I could describe myself as a nearly 30 year old .NET developer from Sweden, with a passion for pretty much everything in the software engineering / craftsmanship department (hey, why limit yourself to one kind of cake when there’s so much to be had out there!). I am a strong advocator of Open-Source Software and I head the MEF Contrib project, a set of community contributed extensions, tools and samples for the Managed Extensibility Framework, and I have also created the Common Service Factory, a WCF extension that enabled dependency injection in services (it’s a bit dated, but it works like a charm – probably should give it some love as soon as I can find a slice of spare time in my life). Oh yeah, there’s more to me than being a code ninjah – somehow I’ve also managed to get married to my high school sweetheart (12 years since we hooked up and still going strong) and together we have two wonderful boys (3 and 1½ years old – boy do they know how to keep us busy hehe) Well I guess that’s it… now you know a bit about me, and I hope to get to know a bit more about you, the readers of Elegant Code, so please stop by my posts and drop me a line or two. See you there!]]> http://elegantcode.com/2010/08/15/i-guess-an-introduction-is-in-order/feed/ 2 What Does Elegant Code Mean to Me? http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/?utm_source=rss&utm_medium=rss&utm_campaign=what-does-elegant-code-mean-to-me http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/#comments Fri, 09 Apr 2010 19:46:38 +0000 John Sonmez http://elegantcode.com/?p=3434 What is elegance? Simply stated. Something that is simple yet effective, delivered with grace. Being simple is not enough. Simple lacking effectiveness is just a waste of time. Simple - Not Effective Simple, but not effective is a foam hammer. You don't want your code to be like a foam hammer. If it can't do what it supposed to do the simplicity just looks like stupidity instead. Effective, but not simple is something that gets thrown away or lamented. It's a Rube Goldberg machine. Rube Goldberg Machine You don't want your code to be like a Rube Goldberg machine either.  Where people look at your code because it is such a spectacle.  You don't want someone to look at your code and immediately think they want to kill you.  Code that evokes murderous rage, tends to get blamed for anything that goes wrong in the system, even if it works perfectly. If you can build something simple and its effective, it still has to be delivered in a graceful way. Consider, the elephant harness... Simple and Effective - Not Graceful Simple?  Yes, it's a box strapped on top of an Elephant, can't get much more simple than that.  Effective?  Yes, looks to me like that elephant will get you where you need to go in that terrain.  Delivered with grace?  Hmm...  Do you want to ride around on an elephant? Even if you nail the first two, with your code, you should make sure it looks and reads good.  No one wants to ride an elephant.  I have seen more than one simple effective design get thrown away because the variables were named things like "cntr" and "banana".

Elegant Code is James Bond

Women love him, men want to be like him and he kills people with a simple sophistication. When people read your code they should think James Bond, not Booger from Revenge of the Nerds. James-Bond Vs. booger
Elegant code to me is code that reads well, does what is is supposed to do and is easy to maintain. Now that I have told you what I think elegant code is, in future posts I will talk more about how to actually write elegant code.

Side Note - Joining Elegant Code

First of all I wanted to publicly thank the other Elegant Coders for inviting me to join their community. I feel honored and esteemed to be joining such a great group of software craftsmen. I also wanted to clear up confusion for anyone who has been following my blog at http://simpleprogrammer.com.  I will still be blogging there, so don't change your RSS feeds, but in addition I will be blogging here at ElegantCode.com.  If you've come here form a link on my personal blog, I encourage you to check out the other excellent bloggers on this site and consider adding Elegant Code to your RSS feed reader.   My personal blog will contain a wider array of topics, but my content here at ElegantCode.com will be centered around the theme of writing elegant code. As always, feel free to email me at john *dot* sonmez *at* gmail.com or follow me on twitter.]]> http://elegantcode.com/2010/04/09/what-does-elegant-code-mean-to-me/feed/ 1 Welcome Two New Elegant Coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/?utm_source=rss&utm_medium=rss&utm_campaign=welcome-two-new-elegant-coders http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/#comments Thu, 15 Oct 2009 19:58:17 +0000 David Starr http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/ I am happy to introduce 2 new Elegant Coders! We are excited to have their contributions to the site and look forward to their wisdom.

Kirstin Juhl

@kirstinj

We are excited to have Kirstin drop wisdom like she has been doing on her current blog: I [heart] Code. From her own bio:

I am a former engineer who writes code. I did Toyota Operating System, Kanban, and Lean in my factories a decade ago, and am fascinated by its use in software development today. You can take the girl out of the factory, but you cannot take the engineer out of the girl, and so I approach everything in life as a problem to solved or optimized. Including software development. I strive to be a craftsman.

I am a mom, and I take lessons from parenthood into my work everyday.

Jason Jarrett

@staxmanade

Jason is a big-time Silverlight maven and the developer behind StatLight, a set of unit testing tools for Silverlight. I knew he was perfect for the tribe when he said, “… and so I added automocking to Unity for Silverlight.”

Yeah. :)

Welcome all.

]]> http://elegantcode.com/2009/10/15/welcome-two-new-elegant-coders/feed/ 0 FubuMVC From Scratch – Part 4 Persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/?utm_source=rss&utm_medium=rss&utm_campaign=fubumvc-from-scratch-part-4-persistence http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/#comments Wed, 25 Mar 2009 21:22:00 +0000 Ryan Kelley http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/ Previous posts in series:

Persistence is a requirement in virtually every application that we write today, and now the time has come for us to add a persistence model to our FubuMVC app. I know I mentioned moving my samples to the FubuCart source, but I am going to go ahead and implement the persistence piece in the same project the previous articles using, FubuSample. I have also added all the code for this series to the FubuMVC-Contrib project

We will be implementing our persistence model to use NHibernate, Fluent NHibernate, Repository Pattern and UnitOfWork pattern all on top of SQL Express or standard. This will also work for sqllite and other database servers.

Class and Interfaces we have to implement:

  • ISessionSourceConfiguration
  • SQLServerSessionSourceConfiguration
  • IUnitOfWork
  • INHibernateUnitOfWork
  • NHibernateUnitOfWork
  • IRepository
  • NHibernateRepository
  • DomainEntity
  • IDomainQuery
  • FubuSamplePersistenceModel

Note: I put the first two in the list in my Core.Config namespace, and the rest in Core.Persistence

Before we start you probably want to go ahead and add the following references to your core project and Web project

FubuMVC-Persist-Ref

Let’s just work our way down the list and get these files implemented.

ISessionSourceConfiguration

public interface ISessionSourceConfiguration
{
    bool IsNewDatabase { get; }
    ISessionSource CreateSessionSource(PersistenceModel model);
}

SQLServerSessionSourceConfiguration

public class SQLServerSessionSourceConfiguration : ISessionSourceConfiguration
{
    #region Implementation of ISessionSourceConfiguration
 
    public bool IsNewDatabase
    {
        get { return false; }
    }
 
    public ISessionSource CreateSessionSource(PersistenceModel model)
    {
        var properties = GetProperties();
        var source = new SessionSource(properties, model);
 
        create_schema_if_it_does_not_already_exist(source);
 
        return source;
    }
 
    private void create_schema_if_it_does_not_already_exist(ISessionSource source)
    {
        if (IsNewDatabase) source.BuildSchema();
    }
 
    protected IDictionary<string, string> GetProperties()
    {
        MsSqlConfiguration config = MsSqlConfiguration.MsSql2005;
        config.ConnectionString.FromConnectionStringWithKey(“MYDBKEY”);
        config.ShowSql();
        config.UseOuterJoin();
 
        return config.ToProperties();
    }
    #endregion
}

A quick note here: We told SQLServerSessionSourceConfiguration to use a connection string from the app settings file (Web.Config) with a key of “MYDBKEY” This will be important later.

IUnitOfWork

public interface IUnitOfWork : IDisposable
{
    void Initialize();
    void Commit();
    void Rollback();
}

INHibernateUnitOfWork

public interface INHibernateUnitOfWork : IUnitOfWork
{
    ISession CurrentSession { get; }
}

NHibernateUnitOfWork

public class NHibernateUnitOfWork : INHibernateUnitOfWork
{
    private ITransaction _transaction;
    private bool _isDisposed;
    private readonly ISessionSource _source;
    private bool _isInitialized;
 
    public NHibernateUnitOfWork(ISessionSource source)
    {
        _source = source;
    }
 
    public void Initialize()
    {
        should_not_currently_be_disposed();
 
        CurrentSession = _source.CreateSession();
        begin_new_transaction();
 
        _isInitialized = true;
    }
 
    public ISession CurrentSession { get; private set; }
 
    public void Commit()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Commit();
 
        begin_new_transaction();
    }
 
    private void begin_new_transaction()
    {
        if (_transaction != null)
        {
            _transaction.Dispose();
        }
 
        _transaction = CurrentSession.BeginTransaction();
    }
 
    public void Rollback()
    {
        should_not_currently_be_disposed();
        should_be_initialized_first();
 
        _transaction.Rollback();
 
        begin_new_transaction();
    }
 
    private void should_not_currently_be_disposed()
    {
        if (_isDisposed) throw new ObjectDisposedException(GetType().Name);
    }
 
    private void should_be_initialized_first()
    {
        if (!_isInitialized) throw new InvalidOperationException("Must initialize (call Initialize()) on NHibernateUnitOfWork before commiting or rolling back");
    }
 
    public void Dispose()
    {
        if (_isDisposed || !_isInitialized) return;
 
        _transaction.Dispose();
        CurrentSession.Dispose();
 
        _isDisposed = true;
    }
}

IRepository

public interface IRepository
{
    void Save<ENTITY>(ENTITY entity)
        where ENTITY : DomainEntity;
 
    ENTITY Load<ENTITY>(Guid id)
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>()
        where ENTITY : DomainEntity;
 
    IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery)
        where ENTITY : DomainEntity;
 
    void Delete<ENTITY>(ENTITY entity);
 
    void DeleteAll<ENTITY>();
}

NHibernateRepository

public class NHibernateRepository : IRepository
{
    private readonly INHibernateUnitOfWork _unitOfWork;
 
    public NHibernateRepository(INHibernateUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public void Save<ENTITY>(ENTITY entity) where ENTITY : DomainEntity
    {
        _unitOfWork.CurrentSession.SaveOrUpdate(entity);
    }
 
    public ENTITY Load<ENTITY>(Guid id) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Load<ENTITY>(id);
    }
 
    public IQueryable<ENTITY> Query<ENTITY>() where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>();
    }
 
    public IQueryable<ENTITY> Query<ENTITY>(IDomainQuery<ENTITY> whereQuery) where ENTITY : DomainEntity
    {
        return _unitOfWork.CurrentSession.Linq<ENTITY>().Where(whereQuery.Expression);
    }
 
    public void Delete<ENTITY>(ENTITY entity)
    {
        _unitOfWork.CurrentSession.Delete(entity);   
    }
 
    public void DeleteAll<ENTITY>()
    {
        var query = String.Format("from {0}", typeof(ENTITY).Name);
        _unitOfWork.CurrentSession.Delete(query);   
    }
}

DomainEntity

Note: I put both of these classes in my Core.Domain namespace, also XML comments are in Source Repository

public class DomainEntity : IEquatable<DomainEntity>
{
    public virtual Guid ID { get; set; }
 
    public virtual bool Equals(DomainEntity other)
    {
        if (ReferenceEquals(null, other)) return false;
        if (ReferenceEquals(this, other)) return true;
        return other.ID.Equals(ID);
    }
 
    public override bool Equals(object obj)
    {
        if (ReferenceEquals(null, obj)) return false;
        if (ReferenceEquals(this, obj)) return true;
        if (obj.GetType() != GetType()) return false;
        return Equals((DomainEntity)obj);
    }
 
    public override int GetHashCode()
    {
        return ID.GetHashCode();
    }
 
    public static bool operator ==(DomainEntity left, DomainEntity right)
    {
        return Equals(left, right);
    }
 
    public static bool operator !=(DomainEntity left, DomainEntity right)
    {
        return !Equals(left, right);
    }
}

IDomainQuery

public interface IDomainQuery<ENTITY>
    where ENTITY : DomainEntity
{
    Expression<Func<ENTITY, bool>> Expression { get; }
}

FubuSamplePersistenceModel

namespace FubuSample.Core.Domain.Persistence
{
    public class FubuSamplePersistenceModel : PersistenceModel
    {
        public FubuSamplePersistenceModel()
        {
            addMappingsFromThisAssembly();
        }
    }
}

Now that we have all the puzzle pieces in place we need to hook them up and make them do some work. Open up FubuSampleWebRegistry

And add the following code:

protected override void configure()
{
    ForRequestedType<ISessionSourceConfiguration>().AsSingletons()
        .TheDefault.Is.OfConcreteType<SQLServerSessionSourceConfiguration>();
 
 
    ForRequestedType<ISessionSource>().AsSingletons()
        .TheDefault.Is.ConstructedBy(ctx =>
                                     ctx.GetInstance<ISessionSourceConfiguration>()
                                         .CreateSessionSource(new FubuSamplePersistenceModel()));
 
    ForRequestedType<IUnitOfWork>().TheDefault.Is.ConstructedBy(ctx => ctx.GetInstance<INHibernateUnitOfWork>());
 
    ForRequestedType<INHibernateUnitOfWork>().CacheBy(InstanceScope.Hybrid)
        .TheDefault.Is.OfConcreteType<NHibernateUnitOfWork>();
 
    ForRequestedType<IRepository>().TheDefault.Is.OfConcreteType<NHibernateRepository>();
}

With a little luck and all of our mad skills, we should be able to talk to the database now. So we need to plumb our simple product object up to talk to NHibernate. We will do this with a mapping file, and since we are using FluentNHibernate we can do this strongly typed.

Make the following modifications to Product: Extend DomainEntity and get rid of Id Property, it is inherited

public class Product : DomainEntity
{
    public virtual string Name { get; set; }
    public virtual string Description { get; set; }
}

Add mapping file for Product:

namespace FubuSample.Core.Domain.Mapping
{
    public class ProductMap : ClassMap<Product>
    {
        public ProductMap()
        {
            Id(e => e.ID).GeneratedBy.GuidComb();
 
            Map(p => p.Name);
            Map(p => p.Description);
            
        }
    }
}

You may also want to setup your connection string at this point in the Web.Config file, mine looks like this:

<add name="MYDBKEY" connectionString="Data Source=LOCALHOST;initial catalog=FubuSample;Integrated Security=SSPI;" providerName="System.Data.SqlClient" />

I also created an empty database in my local SQL Server instance called “FubuSample” And then I went back to SQLServerSessionSourceConfiguration and changed the value of IsNewDatabase to return true. This will create the schema for the database when the application first runs. There is a multitude of different ways that we can handle this, but this was easy for the tutorial purposes.

Next we will add a behavior to our core project and tell FubuMVC to apply that behavior to all or our ControllerActions.

Create a class named “access_the_database_through_a_unit_of_work” in your Core.Web.Behaviors namespace. The contents will look like this:

public class access_the_database_through_a_unit_of_work : IControllerActionBehavior
{
    private readonly IUnitOfWork _unitOfWork;
 
    public access_the_database_through_a_unit_of_work(IUnitOfWork unitOfWork)
    {
        _unitOfWork = unitOfWork;
    }
 
    public IControllerActionBehavior InsideBehavior { get; set; }
    public IInvocationResult Result { get; set; }
 
    public OUTPUT Invoke<INPUT, OUTPUT>(INPUT input, Func<INPUT, OUTPUT> func)
        where INPUT : class
        where OUTPUT : class
    {
        _unitOfWork.Initialize();
 
        try
        {
            var output = InsideBehavior.Invoke(input, func);
            Result = InsideBehavior.Result;
 
            _unitOfWork.Commit();
 
            return output;
        }
        catch
        {
            _unitOfWork.Rollback();
            throw;
        }
        finally
        {
            _unitOfWork.Dispose();
        }
    }
}

Now to tell FubuMVC what to do, open up Global.asax.cs or your Bootstrapper, wherever you are doing the configuration of FubuMVC. In this project we are doing it in Global.asax.cs Add a new behavior to the section that starts with “x.ByDefault.EveryControllerAction” so it looks like this:

x.ByDefault.EveryControllerAction(d =>
   {
       d.Will<execute_the_result>();
       d.Will<access_the_database_through_a_unit_of_work>();
   });

The last thing we will do is open up HomeController and add this code above the Index action:

private IRepository _repository;
 
public HomeController(IRepository repository)
{
    _repository = repository;
}

I also modified the Index action to go ahead and create some database values before we query for them just so we can test this thing. (I only did this for the tutorial, I swear) So modify the Index action to look like this:

public IndexViewModel Index(IndexSetupViewModel inModel)
{
    var prod1 = new Product {Name = "TestProduct1", Description = "This is a test product"};
 
    _repository.Save(prod1);
 
    var prod2 = new Product {Name = "TestProduct2", Description = "This is a test product"};
 
    _repository.Save(prod2);
 
    var outModel = new IndexViewModel();
 
    var productList = _repository.Query<Product>();
 
    outModel.Products = productList.ToList().Select(x => new ProductDisplay(x));
 
    return outModel;
}

Now with you should be able to run your web app and browse to /home and all this will be executed and you will be on your way to creating a whole bunch of persist able objects for use with your FubuMVC app.

As always, feedback is welcome.

]]> http://elegantcode.com/2009/03/25/fubumvc-from-scratch-part-4-persistence/feed/ 9 It’s Official – New Gig started last week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/?utm_source=rss&utm_medium=rss&utm_campaign=its-official-new-gig-started-last-week http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/#comments Tue, 24 Feb 2009 19:03:21 +0000 Ryan Kelley http://elegantcode.com/2009/02/24/its-official-new-gig-started-last-week/