High level goals: building rich apps with same people, same skills, same workflow and common code.
Shows how to decide when to use Silverlight and when WPF.
Moving from Silverlight to full .NET is easier than the contrary. From Full .NET to SL: You need to "unlearn" many APIs. Shared knowledge, but porting code is not easy-
Ian codes an application in WPF then copy/pastes to WPF, UI works pretty much the same way, same controls.
Uses WebClient to make a request to Twitter. WebClient class is very consistent in WPF and SL. Must use asynchronous request in WebClient because SL only supports async.
In Silverlight, we are restricted by security restrictions. Since Twitter doesn't have a cross domain policy, Silverlight cannot access it. This is the big "oh crap" moment :)
Shows templating in Silverlight using VisualStateManager VSM. Since this doesn't exist, use a codeplex open source VSM implementation for WPF. Note: VSM will be included in WPF futures.
Shows how to extend the codeplex WPF VSM. This will be done in future releases of the WPF VSM, but for the moment need some manual coding.
Print | posted on Tuesday, October 28, 2008 12:20 AM