Kick Spy!, Kick Zeitgeist and Kick Widgets
marcinbudny.blogspot.com — In this post I experiment with MetaLinq in order to pass data filter criteria from a client to a service read more...
weblogs.asp.net — From ScottGu's blog. Brand new, Free, ASP.NET 3.5 chart control. It looks very nice! read more...
marcinbudny.blogspot.com — In this post I suggest an implementation of Circuit Breaker pattern with aspect oriented programming read more...
blogs.msdn.com — 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 read more...
sidarok.com — What do we want to see in the next version of Linq to SQL ? read more...
johnpapa.net — Windows Live Writer PlugIn for DotNetKicks is now on CodePlex read more...
ilmatte.wordpress.com — The first part of a tutorial about setting up and configuring CruiseControl.NET. read more...
devlicio.us — 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. read more...
Sponsored Link: www.carlist.ie
Ads via The Lounge