DataObjects.NET: good (flawless, documented, supportive) ORM?

Question

I am looking for an ORM framework, came to NHibernate, Genome, L2S, Entity Framework and now DataObjects.NET. So far I have read documentation that seems pretty affordable, but have you ever tried this ORM?

Any problems / errors with DO.NET would be related :)

Answer 1

I used DataObjects.Net v4. It supports VS 2010 and .Net 4.0, and it is a really good ORM. It is easy to use and automatically creates a database, so you do not create a database and do not reverse engineer it into classes, like some other ORMs. The only thing that was so annoying was the session management and switching mechanism in the case of web applications. I think that even this will be taken care of in version 4.4, which is under development.

Answer 2

I think you should take a look at LLBLGen Pro . I think this is probably the best .NET ORM.

Answer 3

Besides the fact that this question sounds very similar to the information one, there is a big problem with DataObjects.Net - it has a dual license like GPL or commercial without evaluation. So the answer is no, I have not tried it, and it is unlikely that I will try it .

I don’t have beef with the GPL (although I don’t like it for various reasons) or with two licensed products - after all, choosing a license is the right of the copyright holder. However, I also want to reserve this right for my software. I write commercial software that I have no problem with as open source, but under a license of my choice. If I have to accept the new ORM, I want to, no, I need to be able to issue a CTP preview of my product to a limited set of clients for real-time testing. And this will mean that I either have to spend money on DO.Net, not knowing if my investments will bring me; or I have to publish my sources under a license, which actually takes my control of my application from me and can ruin my business by streamlining my product.

Now, if there was a limited evaluation license, say that for non-commercial use within one month, I could consider a quick check and see how it works.

If a product wants commercial adoption, it should have a risk-free way for early adopters to evaluate it.

Answer 4

Does DataObjects.NET support SQL authentication columns? I abandoned v3 because I could not find a way to support identity columns.