We had an interesting internal discussion about ORMs (Linq to SQL, Entity Framework, …) and MicroORMs (Dapper, Massive, PetaPoco, …). This discussion led me to think about: When should I use a MicroORM?
I would go for the approach: Use both (MicroORM and BigORM) and use them where they make sense.
*Updated* 14 November 2011: Video is not on vimeo anymore but on tv.ssw.com
The video video recording of my talk "Continuous Delivery with TFS, msbuild and msdeploy" is finally online.
Please say "Thanx" to Raj.
Thanks to Adam Cogan for introducing me so nicely, he almost got my last name right this time 
The video is on tv.ssw.com -> which just launched BTW and is a great learning resource)
and embedded here
Have fun and send me some feedback
My related blog posts about Continuous Delivery
Index of series
Part 1 ASP.NET - 4 essential steps before going live
Part 2 ASP.NET - 8 performance tips before going live
Part 3 ASP.NET - 9 User Experience tips before going live (*this post*)
The last part of this series focuses on User Experience (UX). From Wikipedia we learn that User Experience stands on 3 pillars:
In this post I want to explain why I don't like debugging, and prefer instead to use unit testing where I work in tiny sections.
To put this post in context, can first I encourage you to read:
I wait here in the meantime 
We just faced an interesting problem on one of our dev's computers.
He is not able to debug any VS2010 solution: Windows Forms, WPF, Web Forms… There is no chance to debug anything on his 64bit machine.
