These old forums are deprecated now and set to read-only. We are waiting for you on our new forums!
More modern, Discourse-based and with GitHub/Google/Twitter authentication built-in.

All times are UTC - 5 hours [ DST ]



Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 
Author Message
 Post subject: ADO.Net 3.0 Entity Framework, the end of NHibernate?
PostPosted: Wed Jul 12, 2006 1:26 am 
Newbie

Joined: Thu Nov 17, 2005 6:37 pm
Posts: 13
Hi,
I've been evangelical about using NH over the last 18 months, but now believe the ADO.Net 3.0 Entity Framework (combined with LINQ) will make NH redundant for .net developers. Am i wrong?

If you read the documentation http://weblogs.asp.net/fmarguerie/archi ... ments.aspx

it's pretty clear MS are taking this seriously.

VS.Net Orca looks like it will contain built in support for modelling the mapping layer, generating object models etc. etc. tools which are sorely lacking for NH communitey (yes, i know there are codesmith templates etc. but on fully integrated support).

From the doco :http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvs05/html/nxtgenda.asp

"Automatically Generated Classes
Having the conceptual level is indeed sufficient for many applications as it provides a domain model that is live within the context of a comfortable pattern (ADO.NET commands, connections and data readers) and allows for great late bound scenarios since return values are self describing. Many applications, however, prefer an object programming layer. This can be facilitated through code generation driven from the EDM description. Within Visual Studio, one can leverage an ADO.NET aware build task to generate the corresponding code. For increased flexibility and data independence between the object and conceptual level, there may be another level of mapping between classes and the conceptual model. This would enable applications built against these classes to be reused against versions of the conceptual model provided a legal map can be defined. For the mapping between classes and the conceptual model the constraints are minimal and are along the lines of preserving identity and fidelity of round trips. The following diagram illustrates the classes from same solution."

This is potentially even more powerful than NH. We have a conceptual model that maps to various physical and logical views of an entity. The domain model is not therefore restricted by such modelling, so we can creatre rich object models using the mapping approach.

We also get built in visual mapping and code generation tools etc. etc.

What do others thing, is this really the end of NH??


Top
 Profile  
 
Display posts from previous:  Sort by  
Forum locked This topic is locked, you cannot edit posts or make further replies.  [ 1 post ] 

All times are UTC - 5 hours [ DST ]


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
© Copyright 2014, Red Hat Inc. All rights reserved. JBoss and Hibernate are registered trademarks and servicemarks of Red Hat, Inc.