DotNetKicks.com : Stories kicked by busior

Using MetaLinq to simulate NHbernate's DetachedCriteria in EF

Thu, 27 Nov 2008 23:30:39 GMT

In this post I experiment with MetaLinq in order to pass data filter criteria from a client to a service

New ASP.NET Charting Control

Tue, 25 Nov 2008 16:31:03 GMT

From ScottGu's blog. Brand new, Free, ASP.NET 3.5 chart control. It looks very nice!

Circuit Breaker pattern AOP style

Mon, 24 Nov 2008 21:52:16 GMT

In this post I suggest an implementation of Circuit Breaker pattern with aspect oriented programming

Persistence Ignorance (POCO) Adapter for Entity Framework V1

Wed, 10 Sep 2008 07:03:07 GMT

One of the limitations of Entity Framework V1 released as part of .NET Framework 3.5 SP1 and Visual Studio 2008 SP1 is lack of support for POCO entity objects. POCO stands for Plain Old CLR Object and refers to an object that does not have any persistence concerns and is not aware of persistence framework. Modern development approaches such as DDD (Domain-Driven Design) and TDD (Test-Driven Development) prefer clear separation of concerns which implies persistence ignorance. [...] We have recently published a sample called EFPocoAdapter that includes code generator and a supporting library that implements POCO object tracking on top of Entity Framework V1

Linq to SQL Wish List

Thu, 05 Jun 2008 08:46:02 GMT

What do we want to see in the next version of Linq to SQL ?

Windows Live Writer PlugIn for DotNetKicks on CodePlex

Wed, 04 Jun 2008 18:31:03 GMT

Windows Live Writer PlugIn for DotNetKicks is now on CodePlex

CruiseControl.Net Tutorial - Part 1

Mon, 02 Jun 2008 23:01:02 GMT

The first part of a tutorial about setting up and configuring CruiseControl.NET.

NHibernate 2.0 Supa' Layer

Thu, 03 Apr 2008 20:46:03 GMT

Essentially I wanted a way to make queries work better within the context of a Domain Driven Design approach. I'm a big believer in Persistence Ignorance, so this means that I had to find a way to represent queries in a provider independent way. LINQ does this for me, mostly, but I still need a 'syntactically pleasing' way to get the LINQ provider to the query at runtime. Well, it turns out that doing this is pretty easy.