Few Differences between WPF and Silverlight

19. April 2011
Comments (0)

 

  1. WPF is a thick Windows client platform, SilverLight is a browser based plug-in. WPF is built on top of .Net Framework and that has access to the full .Net Framework APIs. Silverlight has access to only a subset of the .Net Framework (called the CoreCLR). 

  2. Silverlight is just a subset of WPF.

  3. Silverlight is meant to for web based application (that can run out of browser), while WPF is for desktop applications.

  4. Silverlight is compatible with multiple browsers, devices and operating systems, bringing a new level of interactivity wherever the Web works.

  5. Within WPF, all visually rendering elements derive from the 'Visual' class. Within Silverlight, they do not; Both technologies, however, eventual derive from the DependencyObject class up the hierarchy.

  6. WPF supports 3 types of routed events (direct, bubbling, and tunneling). Silverlight supports direct and bubbling only (so there is no Preview___ events).

  7. There's quite a few data-binding differences. Currently, Silverlight doesn't support the binding mode, OneWayToSource. In addition, Silverlight defaults to OneWay databinding if none is set, while WPF uses the default mode specified by the dependency property.

  8. Silveright doesn't support MultiBinding.

  9. Silverlight supports the XmlDataProvider but not the ObjectDataProvider. WPF supports both.

  10. Silverlight supports browser interop, more media streaming options including timeline markers, and Deep Zoom. WPF doesn't support these features yet.

  11. Silverlight 5(Beta) got XAML debugging support, which is not available in WPF.

Silverlight, wpf ,