Why is WPF losing ground with Silverlight 4?

Question

Possible duplicates:
What else can WPF offer for Silverlight 4?
Why switch from WPF to Silverlight 4

I am working on a WPF application. We looked at using Silverlight instead of WPF, but decided that we wanted to use a full-blown desktop application with all the unique sensations and benefits of the desktop applications that provide. However, starting today, there has been a lot of noise when Silverlight 4 is announced at PDC09, and people claiming there are few arguments left to choose WPF over Silverlight (4).

So what is the buzz about Silverlight 4? Why can Silverlight now be used instead of WPF? And when will WPF still be used?

Answer 1

Fuzz is that Silverlight 4 will have many of the most commonly used WPF features that were previously missing.

The reason for using Silverlight 4 instead of WPF is now the ability to run outside the browser and access a local file file.

WPF should be used when you need features not available in Silverlight 4. See the answers to this question for a discussion of which features are available.

Answer 2

I am only thinking about why, but I would suggest that the recent Silverlight 4 ad is simply because this is the last thing to be announced. WPF has its share of updates in .NET 4.0, so I don’t think it will be anywhere.

One of the biggest differences between Silverlight and WPF is that Silverlight is an isolated file , so I still see a place for WPF in desktop applications.