Another big issue is that EF won't allow you to map an entity that uses a database synonym.

On Apr 12, 2011 11:04am, "José F. Romaniello" <[email protected]> wrote:
I wrote some missing points of EF here:
http://jfromaniello.blogspot.com/2011/03/entityframework-41-rc-code-first-review.html


there is a lot of more things missed.. But If i can't map that simple 4 classes domain... As I said somewhere, I don't find any technical reason to use EF over NH and i found a lot of reasons to not use EF.


2011/4/12 Gerben Rampaart [email protected]>

Hi Guys,



I like NH and have completed several enterprise-size apps with it

succesfully. So I am a fan.



The thing is; our business is at a point where a decision has to be

made between EF and NH.



Can you help me sell NH on a business level to my management? Has

there been research into development-time reduction? Are there charts?

(they always do well :)



So basically anything you guys can offer me which I can use to

convince a non-technical person that NH is the right choice will be

greatly appreciated.



Thanks!

Gerben.



--

You received this message because you are subscribed to the Google Groups "nhusers" group.

To post to this group, send email to [email protected].

To unsubscribe from this group, send email to [email protected].

For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.










--

You received this message because you are subscribed to the Google Groups "nhusers" group.

To post to this group, send email to [email protected].

To unsubscribe from this group, send email to [email protected].


For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.




--
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en.

Reply via email to