.net - Dual-deploying a WPF app natively and as a XBAP -


How to create a WPF application that is a bit uppercase form as XBAP or as original Windows application as possible Can be deployed in? XBAP binary is compatible with WPF Windows applications and move above the same CLR (as opposed to Silverlight). They are still different in some ways.

The biggest difference from the deployment point of view is that an XBAP has page control in the form of a main container, while a Windows application has window controls. This windows application will be too little to use page control, but I feel that it is uncomfortable to use the Page Navigation method in a Windows application (feel free to disagree).

The second major difference is that by default, XBAP is executed in partially reliable environment. It can be interrupted though and XBAPs can be run in complete trust mode. Partial Trust Mode with XBAPs means that you can not use directly from XBAP for remote web services or original code.

What would be an easy and consistent way to achieve the following with the above issues?

Requirements

  1. Deployment in both ways: as XBAP at http and a single WPF executable.
  2. Shows information via a remote web server like Flickr or an unmanaged API.
  3. If possible, the methods of deployment should be loyal to their platform. This means that use pages in XBAP, where they understand and dialogue in the Windows app, where they understand. Platform optimized. XBAP must not necessarily affect the Windows client and vice versa.
  4. Deployment options share as much code as possible. It helps in testing and maintenance.
  5. Running XBAP should be as simple as possible. Certificate attribution will beat the purpose of an XBAP.

What I have collected is that for the first requirement, two separate projects are required. Second restriction can be worked on a user control project which includes all UIs and Referenced by two deployment projects. A WCF web service can work around the boundaries of XBAPs.

If there is to employ a solution similar to the lines mentioned above, then the restriction will need some work first because the Windows client can do without the WCF service because it is already running with full confidence mode The third requirement will require some deployment specific code so that all UI codes are not in user control project.

I would like to know which solution can be used to solve these problems, feel free to ignore the partial solution, mainly to interpret the point and "before The idea about this "is to stop the comment. So just to clarify, I am interested in this problem in the all solution, not just those partial solutions.

The reason for this is because the solution means that there is no need to think between the WPF windows app and XBAP because these two can be built with little effort and the client Whoever chooses the best suit for them.

Here's how to use it to create Wpf and Xbap applications:


Comments

Popular posts from this blog

python - Overriding the save method in Django ModelForm -

html - CSS autoheight, but fit content to height of div -

qt - How to prevent QAudioInput from automatically boosting the master volume to 100%? -