On Tuesday 18th, Victor and I will be presenting A Lap Around VS2010. Check which other talks are available and register here . This is the event information: Horario: martes, 18 de noviembre de 2008 16:00 - 22:00 p.m. Lugar: ITTC. Sarmiento 1113 Piso 5. Buenos Aires Argentina. Registración DescripciÃ...

In my very recent previous post I said "mocking and stubbing easier than ever", but actually forgot to mention the stubbing part :S. This one is not new for users of moq-contrib , but we decided to move this to the core Moq library as we get the question on how to stub properties often enough... :) It...

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. Recursive mocks Quite often you have a root mock object from which other mocks should "hang" through property accesses, such as HttpContextBase.Response...

There's been some excitement lately about the introduction of a common IServiceLocator that all major DI containers apparently will provide. Unless you're building an " extensible framework leveraging framework consumer selectable IoC containers ", don't sweat it too much, the interface was NOT created...

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...

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. In order to get MVC to use the new RTM bits of both assemblies (and avoid weird side-by-side errors), you just need to add the following binding...

Here's what we're currently doing: we add an InitializeContext method to all DataContext-derived classes, which is called from all ctors: private void InitializeContext() { #if DEBUG if ( Debugger .IsAttached) { this .Log = new DebuggerTextWriter (); } #endif ... Read full article

In "traditional" OOP, you advertise your class required dependencies via constructor arguments: public Foo(IOutput output, ILogger logger, ...) Typically, the first few lines of code will check that these dependencies are not null. Optional dependencies may be provided as properties, which you can leave...

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. If you're not using any mock/stub framework...

If you're familiar with Moq , you know that it relies on lambda expressions heavily. This is very good as you get full support from intellisense and refactoring features in Visual Studio. However, it also means you're for the most part restricted to setting expectations on things that your code has access...