Hi,

     My company is interested in using WPF and WCF technologies in our projects. We consider using WPF controls from  Intersoft ClientUI framework. I installed your ClientUI 3 RC framework to do some WPF test project.

On your blog you wrote something like:

http://intersoftpt.wordpress.com/2010/04/09/introducing-intersoft-clientui-part-1/

"The philosophy behind ClientUI is that every component under the ClientUI brand should provide a generic set of compatible APIs to support both Silverlight and WPF application development – enabling effortless migration between Silverlight and WPF apps. Simply put, you can think ClientUI as a set of components that support both Microsoft’s client platforms – the Silverlight and WPF 4. As such, when you see a component under the “ClientUI” brand, you will “intuitively” know that you can use the component in either a Silverlight or WPF application."

   After some short investigation I have noticed that support for SilverLight is much better than for WPF e.g.:

• during creating new project for WPF I have fewer options than for Silverlight  , attachements project_template_list_wpf.png, project_template_list_silverlight.png
• some new items templates like Intersoft UXPage, Intersoft UXWindow are not available in WPF projects. Item list for silverlight attach. new_item_list_silverlight.png
• in WPF projects  datasource control are not available: WCFDataSource, XMLDataSource, AstoriaDataSource.

  For me support for WPF seems to be not finished.

  1. Are you going to implement full support for WPF  considering above differences?

  2. Are there any other differences in support for  Silverligh and WPF in your ClientUI framework. Are you going to implement full support for WPF? When ?

Regards,

Mariusz