WPF and Silverlight Toolkit Compatibility

WPF and Silverlight Toolkit Compatibility | Tmao Coders

WPF and Silverlight Toolkit Compatibility | Tmao Coders — Tue, 11 Nov 2008 22:56:25 GMT

PingBack from http://www.tmao.info/wpf-and-silverlight-toolkit-compatibility/

Silverlight Cream for November 12, 2008 -- #426

Community Blogs — Thu, 13 Nov 2008 09:16:59 GMT

In this issue: Silverlight Girl, Mehdi Slaoui Andaloussi, David Anson, Cheryl, Justin Angel, Kathy Kam

re: WPF and Silverlight Toolkit Compatibility

davidjjon77 — Mon, 17 Nov 2008 14:29:37 GMT

Hi Shawn,

Even though WPF is larger and older than Silverlight, it is my opinion that Silverlight will be far more important than WPF in the future and therefore Silverlight should drive the design of WPF and not allow WPF compatibility to cause inferior design decisions in Silverlight. I do feel that Silverlight WPF compatibility is important but I strongly feel that WPF should be the product making the compromises going forward.

David Roh

JK@SilverlightAzure.com

re: WPF and Silverlight Toolkit Compatibility

Colin Blair — Sat, 22 Nov 2008 01:05:49 GMT

I think I have to agree with David here. I am not worried about the Microsoft.* controls not matching the System.* controls. I do care that the System.* controls match each other and that the Microsoft.* controls match each other. The way to completely fix the compatibility problems you already have it to just go ahead and create a set of WPF controls in the Microsoft.* namespace. Then you can add new features to the Silverlight control and at least stub in the methods and properties on the WPF side to make sure that the XAML is staying compatible.

re: WPF and Silverlight Toolkit Compatibility

sburke — Sat, 22 Nov 2008 02:50:01 GMT

Good feedback - thanks everyone.