Quite often developers of desktop / smart client applications find themselves in the role of writing translation layers (GDD calls them Anti-Coruption Layers) that move state from one model to another. CLINQ 2.0 is uniquely adept at this task.

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

I was poking around with CLINQ, trying to figure out where I might be able to use ContinuousCollections when I found a great one: WF tracking services. With CLINQ and WF Tracking, I can write queries against WF activity logs

So I was giving a demo of Continuous LINQ to the folks in the NYC .NET User's Group tonight and, of course, one of my demos failed. I'm going to kill this Murphy guy.

If you are in the NYC area, then you might want to attend my CLINQ session on Feburary 21st.

This blog post contains an explanation of a demo I wrote for the initial release of CLINQ. It uses a WCF Peer Mesh to distribute messages which are then continuously filtered via CLINQ queries

Continuous LINQ (CLINQ) is a library that builds on the LINQ query syntax to allow you to write a query once that continually updates the result set as the source collection (and items within it) are modified

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.

A very common task in data-driven applications is to render lists of data in ledger-style with alternating row background styles/colors. Unfortunately, a lot of the samples for this are wrong and only apply to limited cases.

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