I'm just about ready to start upgrading the demo suite to be compatible with some of the new code I'm writing for CLINQ 1.1 and thought I'd post a preview of Continuous Aggregation
One of the features that I don't see used often enough is the ability to add your own properties and methods to an existing ADO.NET Entity Model through the magic of partial classes. I show some samples of why I use this feature extensively.
I've been evaluating the ADO.NET Entity Framework as something that I might want to replace my existing DLINQ (LINQ to SQL) code. In this article, I'll point out a bone of contention I have with EF and ORMs in general.
In this article, I will be comparing the Object-Relational Modeling features of Rails w/ActiveRecord to the ADO.NET Entity Framework w/LINQ to Entities
In my previous article, I explored a fairly loose comparison based on overall feel and how well each product implemented the MVC pattern. In this article, I examine support for Agile programming with one specific focus: testing.
I've finally decided to take an in-depth look at Ruby on Rails and ASP.NET and do some comparing and contrasting. I will be as objective as possible, and wherever personal opinion enters into it, I'll make a note of it.
This post will compare and contrast LINQ to SQL and LINQ to Entities provided by ADO.NET vNext, giving some information on the situations in which each technology shines and where they don't.
This post will compare and contrast the features of just using raw DLinq and SQLmetal-generated classes with the ADO.NET Entity Framework. I'll also show how the two can work together
