Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The Entity Framework is constantly implementing new features and everything is automated in your project. It is very easy to use Entity Framework, extend and refactor your code. Visual Studio integrates it (Code-First, Database-first, Entity-First...) like a charm. Windows Azure makes easy to deploy and change it. Moreover Visual Studio can generate all your CRUD pages in 3 clicks.</p> <p>I would suggest you use EF but it depends of your project. Can you give us more details about it?</p> <p>You can find lots of comparison charts on Google, for example <a href="http://gergelyorosz.com/2009/08/nhibernate-vs-entity-framework-a-performance-test/" rel="nofollow noreferrer">this one</a> explains performance and <a href="http://www.dennisdoomen.net/2013/03/entity-framework-56-vs-nhibernate-3.html" rel="nofollow noreferrer">this one</a> differences.</p> <p>EDIT:</p> <p>Can you quantify the number of users in your application?</p> <p>When you use Database-First in EntityFramework it is very easy to <a href="http://www.asp.net/web-forms/tutorials/getting-started-with-ef/the-entity-framework-and-aspnet-getting-started-part-7" rel="nofollow noreferrer">import and use stored procedures</a>, for NHibernate it <a href="http://ayende.com/blog/1692/using-nhibernate-with-stored-procedures" rel="nofollow noreferrer">quite simple</a> as well. Note that if you use a lot of stored procedures and not a lot of simultaneous users the choice of a ORM between those two may not be so crucial.</p> <p>Also don't forget the performance of a tool is often based on the way to use it. If you misuse the ORM (e.g. async, lazy/eager loading, base classes, ...) the performance will drastically drop.</p> <p>Perhaps you can instal both of them, look at how they work and check at their roadmap (e.g. <a href="http://entityframework.codeplex.com/wikipage?title=Roadmap" rel="nofollow noreferrer">Entity framework</a>) to check at the evolution and interest.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload