ORM Poll

Looking for some feedback from ASP.NET community - are you using ORM mapping tool and how disconnected your business logic from the persistence during initial development?

To give a hint, I was looking at NHibernate, Microsoft Entities Framework, and in-house grown entities framework based on DB schema-first as opposed to the pure ADO.NET direct access. Thanks.

9 Comments

  • Better look on LINQ, much more interesting than NHibernate.

  • Repository Pattern with NHibernate.

  • @Travis,
    could you expand a little?

  • @Vitaly,
    LINQ in my understanding, is just a syntax sugar to work again something (for example MS Entities Framework) and could be also applied on NHibernate (if it would support it) or any other mapping tool. I absolutely agree that LINQ itself is an interesting approach.

  • Linq to Sql without using the Entities Framework :)

  • @AndrewSeven,
    how would you build the domain objects using Linq to Sql without having DB in place first?

  • All those recommending linq to sql. Have you actually looked at or tried to use it in a multi-tiered (layered) app? It doesn't work well imho. You lose most of the change tracking etc. I wish it did...but it doesn't. I personally like LLBLGen. I have also used subsonic for small projects but I'm not a big fan of active record.

  • @Shawn,
    I am getting the sense that lots of people would have active record pattern and work with the real DB, rather than working with an InMemory presentation of DB. I looked at SubSonic, nice, but it works against DB only. LLBLGen - have to look into that. So far seems like NHibernate is the only that allows to develop the domain objects first and later just map it to the real DB.

  • In our small shop we use XPO from Devexpress. It comes with a class XPObject from where I inherit my class and then I can call the method Save to persist that info. the ORM can be mapped to 10+ database types and the performance is quite good. Can't complain

Comments have been disabled for this content.