Recap:

The Silverlight and WPF platforms are very similar, but they do not have binary compatibility; this means that an assembly compiled for one platform cannot execute on the other platform (Although, the story is a little different in Silverlight 4). You may want to target some or all of your application on WPF and Silverlight for a number of reasons.

Due to the fact that Silverlight and WPF are so closely related, the bulk of your application code can be shared between the two platforms. This encourages heavy use of pattern based development to isolate the logic from the presentation and maximize the separation between UI code and non-UI code.

Elements you can share:

• Presenters
• Controllers
• Models
• Services
• Unit tests
• Simple views, if the XAML used is supported by both Silverlight and WPF.

Elements that are harder to share:

• Complex views (XAML)
• Controls
• Styling
• Animation

Like always, if anyone has any questions feel free ask.

Download the Presentation Source.  This contains the all sample code that I discussed during the presentation.

Useful links:

• The Composite WPF and Silverlight (Prism) website is where you want to start.
• Elegant Code Cast of Prism v2 – David Starr, Scott Nichols, and myself sat down with the Patterns and Practices team to discuss Prism.
• Channel9 has some good videos available to help you understand and get started using Prism.
• WPF Recipes in C# 2008: A Problem-Solution Approach – This is not a Prism book but it is a great book for solving common problems in WPF.