CLINQ v1.x had an implementation of the weak event pattern, but it was custom and difficult to maintain. CLINQ v2.0 uses the weak event pattern implementations that are available to all .NET developers. I discuss this pattern in this blog post.

I haven't said much about CLINQ lately but that's mostly because we've been trying to get v2.0 ready to ship. We're nearly there, so I thought I would start by talking about one of the new features - smart property notifications

Continuous LINQ, a C# 3.5 extension library that enables standard LINQ queries to remain dynamic and continuous long after the initial query, has been updated to version 1.1 and includes a new demo and lots of new features

In this blog post I show you how to create your own continuous aggregates that extend CLINQ with domain-specific functionality like VWAP (Volume Weighted Average Price).

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

Recently I've been asked several times to explain lambdas and illustrate them. Rather than do the typical "hello world" lambda which is often a function to determine if a number is even, I decided to build a VWAP function using lambdas

Andy Conrad is starting a series of articles on the RESTful API that is Astoria and how to serve it up and consume it. Here's my take on this underrated feature of ADO.NET Data Services

I've been doing some work with LINQ lately and I've come across a situation where it behaves differently than one might expect. This post covers the behavior and a potential solution

I wrote an article on the power of language extensions and LINQ, using Continuous LINQ as an example - for Dr. Dobb's Journal. It will be featured in the February 2008 edition, which is on shelves in January 2008.

Typically when encountering a new technology, immediately after deciding if said new technology has business value, I ask the ever-important question: "Can I game with this?"

In a previous blog entry I talked about dynamically updating LINQ queries. I explore this concept further with something I call Continuous LINQ

LINQ is one of the huge new features coming out of the .NET Framework 3.5, but it can be improved upon. One such ways is by using language extensions to create dynamic, "live" views from LINQ queries

Orcas Beta 1 was just released and I decided to install it on VMware instead of Virtual PC. The results were smooth as butter.

I found this screencast showing off the EDM designer that the Entity Framework so sorely needs. The problem? It won't ship with Orcas!

I've been following the development of C# 3.5 (or whatever-the-heck it will be called) as well as the Entity Framework for a while now. It looks as though this CTP finally integrates all the useful bits.

Being a fan of all things new, I've had some experience with the "Orcas" version of C#. It includes a new feature called language extension that is actually the core of how LINQ is able to be implemented. This post compares against ObjC categories

I recently wrote an article for Dr. Dobb's journal detailing a Web 2.0 project that I did with LINQ to SQL and an early CTP of ADO.NET vNext. The article is in the January 2007 edition of Dr. Dobb's.

As you know, I'm cramming to try and finish up the drafts for the SharePoint book. I'm also doing a lot of work with LINQ in my "spare" time... I wondered what might happen if you combine them.

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

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

A few days ago I started toying with the idea of combining the unbelievable in-memory and database query power of LINQ/XLinq/DLinq with the easy binding syntax and powerful, rich GUI of WPF. This blog post is the result

This blog entry will give you a quick introduction to using language extensions in C# 3.0 by extending the string class

This blog entry will illustrate some of the immense power of combining DLinq queries with the on-the-fly XML generation ability that comes with XLinq to create an RSS feed in one "line" of code!