How to create a WPF application that can be deployed as XBAP or as a native Windows application with minimal overhead? XBAPs are binary compatible with Windows WPF applications and run on top of the same CLR (unlike Silverlight). They are still different from each other.
From a deployment point of view, the biggest difference is that XBAP has a Home control as the main container, while a Windows application has a Window control. It would be pretty trivial to get a Windows application to use the Page control, but I feel (feel free to disagree) that using the page navigation method in a Windows application is pretty unintuitive.
The second major difference is that, by default, XBAP runs in a partially trusted environment. However, this can be circumvented, and XBAP can be launched in full trust mode. Partial trust mode using XBAP means that you cannot access, for example, remote web services or native code from XBAP directly.
What would be a simple and convenient way to achieve the following problems?
Requirements
- It is deployed in both directions: both XBAP via http, and as a standalone WPF executable.
- Displays information from a remote web server, such as flickr or through an unmanaged API.
- If possible, deployment methods should remain true to their platforms. That is: use pages in XBAP where they make sense and dialogs in a Windows application where it makes sense.
Limitations
- The platform is optimized. The material required by XBAP should not affect the Windows client and vice versa.
- Deployment options contain as much code as possible. This helps in testing and maintenance.
- Starting XBAP should be as simple as possible. The certificate prerequisite will defeat the purpose of the XBAP.
, , . , . - WCF XBAP.
, , , Windows WCF, . , .
, . . , " ". , , all , , .
, , WPF- Windows XBAP, , , .