What does WPF still have to offer over Silverlight 4?

Question

Given the list of new features announced in Silverlight 4, when is WPF still required?

Answer 1

WPF still has a lot fuller 3D rendering capabilities.

Also even though they announced enhancements to the commanding and binding capabilities, that's no guarantee that it will have the full ability that WPF currently has or will have in the next version

Edit: After playing around with Silverlight 4 beta, it looks like pretty much all of the new features (webcam, file access, full screen keyboard, COM interop, etc) only work when the application is elevated trust, and elevated trust can only be enable when running out of browser. Some of this may change by RTW, but for now, WPF still looks like the only way to do these things inside of a browser window

Answer 2

I've been using mostly XBAPs for browser deployments while waiting for a Silverlight version that includes WPF's full templating and data binding capabilities. Perhaps Silverlight 4 will do it.

Several things that Silverlight 4 definitely won't be able to do are:

• Allow you to seamlessly integrate your WinForms and MFC user interface components with your application
• Efficiently work with data file structures originally defined in C/C++ (with WPF you can simply copy the code across and easily replicate the original C++ code using unsafe and StructLayoutAttribute)
• Include unmanaged C++ code in your application

I have not actually downloaded the Silverlight 4 beta yet, so this list is necessarily incomplete.