There is quite a bit of Entity Framework and NHibernate comparisons on
the web already but all of them cover mostly the technical side of the
question. In this post, I’ll compare these two technologies from
a Domain Driven Design perspective. I’ll step through several code
examples and show you how both of these ORMs let you deal with problems.
- Added `Select *` plugin.
- Added `Duplicate Commands Per Context` plugin.
- Updated ByMethods plugin to show stack traces of commands.
- Added ability of closing/hiding different tabs.
- Added assembly info to methods info view.
- Updated the NuGet Packages
PM> Update-Package DNTProfiler.EntityFramework.Core
Or
PM> Update-Package DNTProfiler.NHibernate.Core
EF6.1.3 just contain fixes to high priority issues that have been reported on the 6.1.2 release. The fixes include
Query: Regression in EF 6.1.2: OUTER APPLY introduced and more compex queries for 1:1 relationships and "let" clauseTPT problem with hiding base class property in inherited classDbMigration.Sql fails when the word 'go' is contained in the textCreate compatibility flag for UnionAll and Intersect flattening supportQuery with multiple Includes does not work in 6.1.2 (working in 6.1.1)"You have an error in your SQL syntax" after upgrading from EF 6.1.1 to 6.1.2
you can Mock the DbSet and even use a nice Nuget’s package called FakeDbSet which has a InMemoryDbSet.