Sharing skills and code with Silverlight and WPF: MIX ‘09 session video and deck
What happens in Vegas doesn’t always stay there. On Friday, I gave a talk at the MIX ‘09 conference about sharing skills and code between Silverlight and Windows Presentation Foundation (WPF).
One of the most important messages that I had during the talk is the flexibility that the Microsoft Client Platform enables: you can be a Rich Internet App developer today, and build an enterprise Line of Business app tomorrow, since so many of the concepts, APIs, and ideas are shared between these frameworks.
Download session deck (4.7 MB PowerPoint 2007)
View the session on the VisitMix.com site: http://videos.visitmix.com/MIX09/T87F
Check out other awesome Silverlight, WPF, and Expression. Hope this helps. Let me know what you think.
Good session vid. What is the plan on moving more controls that are added to Silverlight toolkit to WPF toolkit? I heard a few people, including you, mention the Chart control for WPF. How about the Accordion? How long would you expect something like that to take before being added to WPF toolkit? I understand priorities, features, bugs, feedback, etc. would be variables for this. Any guesstimation?
@shaggygi,
I don’t think there are immediate plans to get these into the WPF Toolkit, but things are always changing and in motion. Once .NET 4 is closer to release, I think the WPF Toolkit plans will be much more clear. Sorry I don’t know more right now!
Great session, this looks to be a very useful approach and shed much light on the confusing compatability story.
Is the demo code available anywhere?
Are there any plans to have some kind of code analysis built into Visual Studio to give guidance on WPF v Silverlight compatability?
@Andrew,
I haven’t been able to turn around the demo code yet. I’ll post it online soon.
I’m not aware of any plans to include WPF v Silverlight guidance in VS.
Jeff,
Just saw your presentation at Mix online this morning, and thought it was great! Our office is currently split on a technological path going forward for the team, Silverlight or WPF. Based on what I saw it feels as if the question is mute. As long as we practice good design patterns, building applications with shared functionality and libraries across platforms is truly achievable, with very little heavy lifting. We can go down the explicit code set for WPF when needing to implement specific functionality that SL cannot provide. Otherwise we can persue the SL path.
I do have a few questions though. How would one handle functionality that is available in SL that is not available in WPF, i.e. deep linking. Granted this is achievable with CL parameters, but is not as clean, and if ClickOnce is utilized it’s impossible. Do you have any suggestions ideas on how one might go about handling that?
Thanks.