Creating a WPF Front End for a Silverlight 3.0 Application

Question

I am considering creating a WPF interface for a Silverlight application. Since Silverlight usually has a smaller set of features, this should be possible, but I'm not sure what the best way is to approach this issue. From the very beginning, let me say that I am currently launching the application from a browser, but it lacks functionality, for example, capturing system keys, which I would like to add, along with some W7 integration.

I previously shared the source between Silverlight and WPF, creating a project for each, and then using "add as link" to link the source files between them. This time I will probably use .NET RIA Services to exchange source and business logic between platforms.

The problem I see is sharing Xaml between projects. It is pretty copy and paste compatible, with the exception of namespaces, but it is not a great way to share resources. Has anyone come up with a good way to share Xaml between Silverlight and WPF?

The last option that crossed my mind was for the WPF application to use the Browser control to host the Silverlight application. Then I can add special Windows features to them. It seems to me the purest way to move from a development perspective and testing. What do everyone think?

Answer 1

Here is a trick you could use.

• , Silverlight Views View Models , WPF.
• Silverlight, WPF.

• UserControl "CustomerView" DataTemplate, , "customerViewTemplate"

• XAML Silverlight WPF :

<ContentControl ContentTemplate="{Staticresource customerViewTemplate}" />

5. Silverlight App.xaml .

<ResourceDictionary Source="MyApp.Views;component/CustomerViewResources.xaml" />

6. WPF App.xaml .

<ResourceDictionary Source="pack://application:,,,/MyApp.Views;component/CustomerViewResources.xaml" />

, , .

, Silverlight UserControl XAML WPF. :

' 'System.Windows, Version = 2.0.5.0, Culture = , PublicKeyToken = 7cec85d7bea7798e" . API ReflectionOnly, ReflectionOnlyAssemblyResolve .

UserControl WPF Grid #, 3 :

'System.Windows.Controls.UIElementCollection.Add(System.Windows.UIElement)' .

'System.Windows.Controls.UserControl' , . 'System.Windows, = 2.0.5.0, = , PublicKeyToken = 7cec85d7bea7798e '

'ToWpfTest.Views.TestView' 'System.Windows.UIElement'

, , System.Windows.UIElement WPF System.Windows.UIElement Silverlight.

Answer 2

XBAP . -, silverlight, , .

W7 ?

, .

, , Xaml . , , . - Xaml Silverlight WPF?

XBAP WPF. 2, . ( , (Window and Page), , 2 .

, , ...

XBAP , ..

• : Composite WPF Silverlight

Answer 3

The problem with XAML sharing is that Silverlight and WPF use very different models to handle animations and state changes. I would suggest that the amount of XAML intended for animation would be quite significant in most projects, so I don't see XAML sharing as a very viable option.