Silverlight 2.0 is a freaking phenomenal RIA development environment and I would actually, at this point, put the development experience in Silverlight 2.0 above and beyond Flex. I can do more faster and have it look better and run more efficiently in Silverlight 2.0 than I can in Flex. BUT, when you're looking for case studies, look for ones where the person or organization who adopted Silverlight did so of their own volition, without being approached by Microsoft. I'm interested in hardcore, unbiased opinions from people who have been in the trenches doing their own coding, not watching Microsoft consultants do the coding for them. There are plenty of case studies like that out there, you just have to look past the shiny bouncing balls that are the Olympics and the Oscars and all the other crap that probably cost Microsoft a hojillion dollars in marketing funds and incentives.

Roughly two years ago, when I was writing an article on 'New Features for Device Developers in Visual Studio 2005' that was published in the August 2005 issues of this magazine, our program management team was already busy shaping the next release of the product, which is soon to be released as Visual Studio 2008. We spent a lot of time talking to our major customers and reviewing the feedback we got on blogs and questions on forums on newsgroups to identify what enhancements/features would be most useful to our device developers. One thing that surfaced was that device developers needed more help when it came to testing their applications efficiently. Whether that meant testing on multiple devices or under varying conditions or simply being able to write unit tests, they clearly needed help getting applications to market faster by reducing the testing time.