Silverlight 3.0 from browser versus WPF / Windows App - Summary of differences?

Thanks to the new Silverlight 3.0 feature, which allows you to host components outside the browser, our company is looking for detailed information about the differences between this new feature and Windows WPF applications (since Silverlight is partly a subset of WPF).

Is there a good resource that lists the differences between Silverlight 3 outside the browser and WPF applications? Areas such as permissions, functionality, etc.

If there are no web resources, what are some of the key differences?

+7
wpf silverlight
source share
3 answers

Silverlight OOB applications have the same capabilities as a Silverlight application in a browser, except that they lose the ability to communicate with the DOM (via the System.Windows.Browser API).

The following is a short list of some common things that you do not have access to Silverlight with that you plan to use in a WPF application:

  • Client file system
  • Windows Client Registry
  • Client Event Log
  • OLEDB Client
  • SQL client client

This may seem like a long list, but it should look familiar enough for a no-to-do list for any web application platform (a la ASP.NET, JSP, PHP).

+11
source share

Jaime Rodriguez has a very good publication highlighting the key differences and features of both Silverlight and WPF: Here . This is a very high level and is designed to distinguish between the features that WPF and Silverlight Out-of-Browser bring to the table.

+3
source share

markti is correct.

Scott Barnes is Rich Platforms Product Manager - Microsoft.

+1
source share

All Articles