A quick disclaimer: we're entering religious territory here. I feel strongly about this issue, but it's certainly my opinion. If you want to get the full sense of how passionate people are about this issue, check out this article at JavaWorld . I've come to the point of view that Entities...

Disclaimer! Ayende rightly points out that if you are testing your queries you get this mapping test for free. If you aren't, well put this in place as a stop gap measure (to test mappings) and if you have queries, which you probably do, get to testin'! A while back Bil Simser put up a post on...

I've written about the template method pattern before. For my money it's still a very useful pattern for building super lightweight frameworks and enabling the open-closed principle which states: Software entities (classes, modules, functions, etc.) should be open for extension, but closed for...

In Domain-Driven Design we turn to the specification pattern when we want to check whether an object matches some criteria. I think specification is the oft-forgotten bastard child pattern of the domain model pattern language. I know I frequently turn to queries -- sometimes query objects -- when I want...

Introduction We used ActiveRecord migrations at Eleutian for a number of months. Everything was right with the world and we had no major complaints until we started running into a problem with our more complex migration scenarios. Usually, we see two kinds of migrations: Schema - Add/remove/rename columns...

I'm very pleased to formally announce a project that Aaron and I started a few months ago and have been quietly contributing to. MultiFunctionMachineMachine , MFMM, or just Machine is a collection of common code and projects that we've collected into one place for our own consumption. In the...

While working on the new product (and that's why the break) we got into a DataBinding situation. We had a DTO class, something like this public class Employee { private string employeeName; private string employeeId; public string EmployeeName { get { return employeeName; } set { employeeName = value...

Many a time you might face this issue. Especially when you are using a third party component, which uses an older version of an assembly, of which you are using a newer version. Pre 2.0 (and I do not know for sure of 2.0) compiler compliant to the CLS do not support the functionality of a static reference...

There were a few mistakes in the last post on the AppDomain.Unload solution (thanks Manoj for pointing out) (John Papa wanted to know why I did not use LoadFile, thanks John, now I know should have written that MarshalByRef, just forgot it completely.) And sorry for this delayed update, damn weekend...