Category Archives: NHibernate

Missing EF Feature Workarounds: Filters

Posted on May 29, 2014 by Jimmy Bogard

Filters are one of those ORM features that when you need it, you REALLY need it. NHibernate has had this feature for quite a long time, but it still doesn’t exist in EF. What are filters? In NHibernate, a filter … Continue reading →

Also posted in Backbone, Javascript, Marionette, Underscore | 20 Comments

Missing NHibernate features in Entity Framework

Posted on May 5, 2014 by Jimmy Bogard

Recently I blogged about migrating to EF from NHibernate and how easy it is to create fully encapsulated models mapped to EF. In this particular project, migrating was relatively painless, as it was a fairly new schema and quite amenable … Continue reading →

| Leave a comment

Domain modeling with Entity Framework scorecard

Posted on April 29, 2014 by Jimmy Bogard

A long, long time ago I had a series on strengthening your domain, highlighting how simple refactoring tools and code smells can help guide your models to push behavior down into your core domain model/business objects/whatever. All the techniques highlighted … Continue reading →

| Leave a comment

Migrating from NHibernate to Entity Framework

Posted on April 22, 2014 by Jimmy Bogard

I’ve been a supporter and user of NHibernate for nearly 10 years. While not part of the original NHibernate Mafia, I’ve long enjoyed NHibernate’s ability to rich, behavioral domain models. I wasn’t happy with the initial designs of Entity Framework, … Continue reading →

Also posted in Backbone, Javascript, Marionette, Pusher, SignalR, Socket.IO, Web Sockets | 12 Comments

Using AutoMapper to perform LINQ aggregations

Posted on April 8, 2014 by Jimmy Bogard

In the last post I showed how AutoMapper and its LINQ projection can prevent SELECT N+1 problems and other lazy loading problems. That was pretty cool, but wait, there’s more! What about complex aggregation? LINQ can support all sorts of … Continue reading →

| Leave a comment

Using AutoMapper to prevent SELECT N+1 problems

Posted on April 3, 2014 by Jimmy Bogard

Back in my post about efficient querying with AutoMapper, LINQ and future queries, one piece I glossed over was how View Models and LINQ projection can prevent SELECT N+1 problems. In the original controller action, I had code like this: … Continue reading →

| Leave a comment

Avoid many-to-many mappings in ORMs

Posted on March 12, 2014 by Jimmy Bogard

Going through and reviewing the Contoso University codebase, really to get caught up on EF 6 features, I found a relationship between two tables that resulted in a many-to-many mapping. We have these tables: A Course can have many Instructors, … Continue reading →

| Leave a comment

NServiceBus and concurrency

Posted on November 1, 2012 by Jimmy Bogard

A while back, Andreas posted on NServiceBus sagas and concurrency. In that post, he described both what to consider and how to change the concurrency model of NServiceBus and how it relates to sagas. One thing that comes as a … Continue reading →

| Leave a comment

ORM techniques for legacy databases

Posted on July 26, 2012 by Jimmy Bogard

One of the reasons folks typically go with a hand-rolled ORM (i.e., using ADO.NET by hand) is the assumption that ORMs don’t work well with legacy databases or databases designed in isolation from any sort of object model used to … Continue reading →

| Leave a comment

Persisting enumeration classes with NHibernate

Posted on May 1, 2012 by Jimmy Bogard

As part of my “Crafting Wicked Domain Models” talk, I walk through the concept of enumeration classes, yanked from Java and on Jon Skeet’s list of biggest C# mistakes (or missing features). In my talk, I leave out how to … Continue reading →

| Leave a comment