The document discusses expanding the reach of apps by using Silverlight and XBAP. It compares the reach, richness, and ease of development between web, Windows, and RIA applications. It then covers the features and differences between WPF, XBAP, and Silverlight frameworks. The document provides tips for recycling code and XAML between the frameworks and announces a local Silverlight user group meeting.

1. Re-use Your Skills and Code to Expand the Reach of Your Apps with Silverlight Frank La Vigne Lead Designer Applied Information Sciences http://www.franksworld.com

2. Ego Slide Frank La Vigne Microsoft MVP: Tablet PC INETA Membership Mentor for DC, Maryland and Delaware Manager/Founder Silverlight SIG Lead Designer @ AIS Blog: www.franksworld.com Company: www.appliedis.com Twitter: @Tableteer Feedback to [email_address]

3. Goals

4. The 3 R’s of Client Development

5. Reach: The Web Widest possible reach From text only devices to desktops; from laptops to mobile phones; the web works just about anywhere Platform/Browser Independent* *Write once, test everywhere in every conceivable combination. Hard to debug Easy to Deploy User experience varies

6. Rich: Windows Client Application Richest experience possible Response time is instantaneous WPF applications can leverage hardware acceleration for some truly engaging user experiences Easy to Debug Narrow focus Deployment concerns

7. RIA: Silverlight Applications Happy Medium of Reach and Rich Response time is instantaneous Runs on Windows, Mac and Linux Easy to Debug Wide focus Easy deployment Enables great user experiences

8. But Wait, There’s More!

9. The Fantastic Four of Client Technology

10. XBAP?

11. XBAP Defined Slightly Better Reach, a Lot More Rich All the benefits of Silverlight The Power of WPF in a browser window 3D, Drag & Drop, Printing, Hardware Acceleration Easy to Debug Easy deployment (Windows w/ .NET 3.x) Enables great user experiences

12. When to Use XBAPs To quickly push a WPF app onto the web When Management demands that applications be web based When Windows is the client platform Ideal for corporate intranet Specialized applications Quickly moving a WPF application to the web

13. "Sawdust"

14. How Can I Create an XBAP? Open Visual Studio 2008 File  New Project  WPF Browser Application

15. How Do I Deploy an XBAP? In Visual Studio 2008 Build  Publish

16. Deploying an XBAP: Mime Types

17. Let the LOLCats Guide Us Creating & Publishing an XBAP Application

18. 3-2-1 Launch!

19. Mostly the Same

20. But the Differences Will Get You

21. Caution: Eye Charts Ahead!

22. Different Feature Sets.. 3D Documents Drag Drop Win32 Interop Triggers Commands Printing Logical tree Adorners Hosting WebBrowser Deep Zoom VC-1 codec HTML integration Sandbox VideoBrush

23. Graphics Hardware acceleration Graphics are Drawings Streams Shapes Multi-core optimizations Lighter weight visuals Graphics are Shapes

24. Property System More inherited properties Extensible Property Metadata Default Values Coercion

25. Resources generic.xaml Delayed instantiation of StaticResources Merged Resource Dictionaries FindResource walks the tree Freezables generic.xaml XamlReader can load Resource Dictionaries.

26. Databinding UIElement to UIElement bindings MultiBinding Binding support at DependencyObject Dictionaries Relative bindings Template selectors More Type converters out of the box Binding support at FrameworkElement No TargetType on data templates

27. Eventing Events are synchronous Tunneling (Preview) events Mouse Wheel Events are asynchronous Not all events bubble, even if declared as Routed

28. Styles Write-once No app themes No BasedOn No triggers

29. Templates No TargetType No template selectors

30. Animation MotionPath Animation CompositionTarget.Rendering More animatable types Extensibility Storyboard APIs added in 3.5 SP1 Named key-frames Storyboard APIs Begin, Stop, etc.

31. Input Support for other platforms Key.Unknown ModifierKeys.Apple KeyEventArgs.PlatformKeyCode

32. Layout LayoutTransform Text measures early

33. Other More markup-extensions e.g. x:Static More panels Different Hit-Testing LayoutRounding Property No XamlWriter No VisualBrush No OnRender

34. Enough Slides! Code Time WPF  XBAP WPF  Silverlight

35. Tips & Tricks for Recycling XAML Source compatibility ( not binary compatibility ) It is a different framework Code to Silverlight (Common Denominator) Create a different VS project for each ‘run-time’ Link the files together Use WPF’s XML namespace declaration xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"

36. Tips & Tricks for Recycling Source Code Use #if for small logic Move all conditional logic to code ( no #if in XAML ) Partial classes for larger chunks Can use separate files altogether Place Templates and styles in App.xaml (both platforms can pick from there)

37. Other API differences OpenFileDialog SL = System.Windows.Controls WPF: Microsoft.Win32 Dispatcher.BeginInvoke different signatures SL has more classes sealed ( can’t be inherited ) XamlReader.Load SL = XamlReader.Load ( string ) WPF = XamlReader.Load ( stream )

38. Other API differences (cont’d) ContentPresenter SL : class ContentPresenter : Control WPF : class ContentPresenter : FrameworkElement UIElementCollection SL : UIElementCollection : PresentationFrameworkCollection<UIElement> WPF : UIElementCollection : IList, ICollection, Ienumerable

39. Silverlight User Group First Meeting is Wednesday, Feb 25 7:00 PM www.caparea.net/silverlight

40. THANK YOU! Frank La Vigne www.FranksWorld.com [email_address]

41. Microsoft.com/tag

42. Session Summary We covered this That And the other thing!

43. For More Information Visit MSDN at http://msdn.microsoft.com More information at: http://anotherUrl Subscribe to my blog: http://msdn.microsoft.com/alias