This sequel explains how to write O/RM specific performance optimizations in such a way that the core business logic won’t be affected. This article builds on top of the foundation described in part 1 and uses the Fetching Strategy design pattern to achieve this goal.
I recently tried to figure out how to write testable code while using LINQ to SQL as my O/RM of choice, without loosing the ability to use LINQ to Expression trees! In this post I describe the design I ender up with.
Roger Alsing wrote an interesting post yesterday about adding support for enums to LINQ queries. It is nice to see what Roger is doing with the .NET 4.0 ExpressionVisitor to change Expression trees that allow this behavior. What I dislike however, is that for this solution you need to reimplement all Queryable extension methods. So I thought about this and found a more pleasant way of intercepting query calls.
This article describes the EntitySorter<T> class. It's a nifty little thing that allows the presentation layer to instruct the service layer how collections should be returned.
Integrating Enterprise Library Validation Application Block With LINQ to SQL and Entity Framework Part 4: Using Metadata to Automate Validations
This article describes how to extract information from your generated LINQ to SQL entities to automate validations like maximum string length and disallowing null values.
For over three years I've been using NDepend. In this post I'll describe my thoughts on NDepend.
Last week I published the first stable release of CuttingEdge.Conditions.
In this post I’ll describe another breaking change I’m making to my open source project, CuttingEdge.Conditions.
In this post I’ll describe a controversial change I’m making in my open source project, CuttingEdge.Conditions.
The Entity Framework Design blog just published a template that enables converting a LINQ to SQL .dbml file to a Entity Framework .edmx file.
Integrating Enterprise Library Validation Application Block with LINQ to SQL and Entity Framework Part 2: Using context within custom validators.
This article describes how to write custom validators for the Enterprise Library Validation Application Block, in such a way that it runs within the context of a specific LINQ to SQL DataContext or Entity Framework ObjectContext class, which allows analysis of non-persisted (in-memory) changes in that context.
Integrating Enterprise Library Validation Application Block With LINQ to SQL and Entity Framework Part 1: Basic Integration
This article describes how to integrate the Enterprise Library Validation Application Block in conjunction with an O/RM technology such as LINQ to SQL and Entity Framework.
The Microsoft ADO.NET team blog made an important announcement yesterday about the future of LINQ to SQL.
In a previous post I introduced CuttingEdge.Conditions, a library that helps developers to write pre- and postcondition validations in their .NET 3.5 code base. In this post I'll explain how you can extend the library.
CuttingEdge.Conditions is a library that helps developers to write pre- and postcondition validations in their .NET 3.5 code base. Writing these validations is easy and it improves the readability and maintainability of code.
The last couple of days I had some spare time. What does a workaholic do with spare time? Exactly: he builds his own library. :-)
I just reported a bug on the Microsoft Connect site about a quirk in the C# IntelliSense feature regarding generic extension methods.
Anders Hejlsberg, lead architect for the C# language at Microsoft, announced early august Microsoft is working on a parallel implementation of LINQ internally known as PLINQ.