Customers often ask about best practices and blueprints on how to build solutions for the cloud (on Microsoft Azure in particular). These days things evolve at a pace never seen before why developing reference architectures may be a very costly thing - once it’s done it may be obsolete if it’s produced with too much detail and too low level of abstraction.

One of my apps, Driver’s Log, is now celebrating three years in the Windows Phone Store. The app has a loyal user base and by continuing adding features and supporting new devices I surly hope that you’ll continue to enjoy it for at least another three years.

Earlier this year I had the pleasure to contribute content to a book on Scrum with Visual Studio

The Continuous Delivery wave seems to be what people are trying to surf these days. I’m a bit worried though when I see posts and articles, especially from the Microsoft Community, where people claim they do Continuous Delivery when in fact the only thing they achieved is an automated deployment triggered by a check-in.

A while ago I wrote an article describing how the Portable Class Library can enable us to write Unit Tests for our Windows Phone apps using the tools and frameworks we’re already familiar with. By adding an abstraction layer and using types common to the Base Class Library, Portable Class Library and Windows Phone we can write unit tests using tools like MSTest and Moq.

As a consultant I travel quite a lot by car. By the end of every month I need to fill in our corporate Excel spreadsheet with my mileage and send it to payroll in order to get reimbursed.

During my parental leave this summer I had some moments which I could spend on coding-for-fun. Like a whole lot of others these days I began to write a couple of Windows Phone 7 apps. Among the first things I looked into was the availability of testing frameworks especially suited for Windows Phone development. Back then I found one – the silverlight toolkit unit testing framework. It’s an impressive piece of work. But in my humble opinion it lacks, currently, two major features. The first feature is; execute unit test outside of the emulator or the device i.e. on your computer.