[http://msdn.microsoft.com/en-us/magazine/dd882515.aspx] <p> [http://msdn.microsoft.com/en-us/magazine/ee310078.aspx] My Data Points column in the August 2009 issue [http://msdn.microsoft.com/en-us/magazine/ee294456.aspx] of MSDN Magazine is now online,titled Data Performance and Fault Strat

Jeremy Miller just published a post asking for feedback [http://codebetter.com/blogs/jeremy.miller/archive/2009/08/02/what-s-hard-about-activating-screens.aspx] on how we activate and deactivate our screens in our application frameworks (what I also call a Presentation Framework). I started replyin

I updated my SilverTwit code for my June 2009 Data Points column in MSDN Magazine [http://msdn.microsoft.com/en-us/magazine/dd882515.aspx] to use the release version of Silverlight 3. The revised code can be retrieved in the codeplex site here [http://code.msdn.microsoft.com/mag200906DataPoints]. Th

Lately I have been immersed in the world of MVVM/Silverlight and often Prism. But in this world the design elements can’t be pushed aside. I admit it … I am a developer who has fallen in love with Blend! So I was pretty unhappy (Ok, I was very frustrated) when I started using Prism apps and breaking

I build a lot of line of business applications and in the process there are always certain aspects I have to tackle that I like to call the presentation framework collectively. Common aspects of a presentation framework are (not a conclusive list, but a good start) * transitions from screen to scr