Daniel Cazzulino's Blog

I've just released a new version of Moq which contains a few bug fixes but two extremely useful features: recursive mocks and mocked default values.

There's been some excitement lately about the introduction of a common IServiceLocator that all major DI containers apparently will provide.

Quite some time ago I posted about how we (Clarius Consulting with Microsoft Patterns & Practices) solved the multiple resolution/orientation problem for Windows Mobile developers by introducing the Orientation Aware Control (OAC) as part of the Mobile Client Software Factory. As any 6-month project, there were a number of features that had to be left out because of time constraints. Also, being two years old also shows: that version does not support smartphone project types, neither Windows Mobile 6, nor VS2008, etc. A few bugs were also discovered after being released....

As you probably know by now (i.e. from Phill's blog), however both Routing and Abstractions are. MVC Preview 4, however, has its own version of both assemblies.

Here's what we're currently doing: we add an InitializeContext method to all DataContext-derived classes, which is called from all ctors:

Query: "how to replace ipod touch boot screen"
Cuil: 1 result, completely unrelated to what I'm looking for
Google: 140k results, including the one I was looking for in the first 10
MS Live: 423k results, the actual answer nowhere to be found in the first 40 results (so, for practical purposes I guess it's the same as Cuil useless result too :))

In "traditional" OOP, you advertise your class required dependencies via constructor arguments:

I've argued in the past that this theoretical discussion is utterly useless. In my experience you need slightly different things from your test doubles at different times and depending on the scenarios and what you care about testing in a particular test.