Gotcha when deploying Silverlight applications

I'm just in the process of writing my first Silverlight post, one of the benefits of writing about Silverlight is that you can show it in action. So last night I put together the working example, and was running into a roadblock at the final stage, deployment.

Using Blog Engine .NET

So I decided to use Blog Engine .NET for the foundation of this blog, I suspect I'll move to something homegrown when I start putting together a product oriented site, but for now it certainly scatches the itch.

Compiled Experience!

As you can see I've moved things to a new blog, with a new name, design and software. For me things like this are fresh starts which help to develop new habits, the excitement of something new means new habits start and with effort I can keep them going.

Implementing an ActiveRecord pattern in Linq to SQL

In earlier posts I talked about about creating Domain Driven Design style repositories using Linq to SQL. These allowed us to swap between Linq to SQL repositories and In Memory ones easily (and really anything that could support IQueryable<T>, this ensured some very nice testabiliy. In this post I thought I'd go over some it again as well as a some refactoring I had done to simplfy things, as well as how to create simple Active Record style data access on top of our repositories and therefore still ensuring our testability.

Lightning does strike twice

So a hard drive was failing (sounding like an angle grinder). Not wanting to risk extracting the data myself before it failed I sent back to the professionals since it was under warranty.