mirror of
https://github.com/Stone-Red-Code/docs-desktop.git
synced 2026-09-05 23:42:58 +02:00
Links: .NET Desktop - framework\wpf (#109)
* Links: .NET Desktop - framework\wpf * Apply suggestions from code review Co-authored-by: Andy De George <[email protected]>
This commit is contained in:
David Coulter
co-authored by
Andy De George
Andy De George
parent
c1d6e1d23e
commit
674b773578
+2
-2
@@ -109,7 +109,7 @@ The resulting code augments your application definition with additional infrastr
|
||||
|
||||
## Getting the Current Application
|
||||
|
||||
Because the functionality of the <xref:System.Windows.Application> class are shared across an application, there can be only one instance of the <xref:System.Windows.Application> class per <xref:System.AppDomain>. To enforce this, the <xref:System.Windows.Application> class is implemented as a singleton class (see [Implementing Singleton in C#](https://docs.microsoft.com/previous-versions/msp-n-p/ff650316(v=pandp.10))), which creates a single instance of itself and provides shared access to it with the `static`<xref:System.Windows.Application.Current%2A> property.
|
||||
Because the functionality of the <xref:System.Windows.Application> class are shared across an application, there can be only one instance of the <xref:System.Windows.Application> class per <xref:System.AppDomain>. To enforce this, the <xref:System.Windows.Application> class is implemented as a singleton class (see [Implementing Singleton in C#](/previous-versions/msp-n-p/ff650316(v=pandp.10))), which creates a single instance of itself and provides shared access to it with the `static`<xref:System.Windows.Application.Current%2A> property.
|
||||
|
||||
The following code shows how to acquire a reference to the <xref:System.Windows.Application> object for the current <xref:System.AppDomain>.
|
||||
|
||||
@@ -387,5 +387,5 @@ Likewise, the following figure illustrates the key events in the lifetime of an
|
||||
- [Navigation Overview](navigation-overview.md)
|
||||
- [WPF Application Resource, Content, and Data Files](wpf-application-resource-content-and-data-files.md)
|
||||
- [Pack URIs in WPF](pack-uris-in-wpf.md)
|
||||
- [Application Model: How-to Topics](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/ms749013(v=vs.100))
|
||||
- [Application Model: How-to Topics](/previous-versions/dotnet/netframework-4.0/ms749013(v=vs.100))
|
||||
- [Application Development](index.md)
|
||||
|
||||
+2
-2
@@ -25,5 +25,5 @@ The following topics show how to create project files for the various [!INCLUDE[
|
||||
- [Building a WPF Application](building-a-wpf-application-wpf.md)
|
||||
- [Deploying a WPF Application](deploying-a-wpf-application-wpf.md)
|
||||
- [Walkthrough: My first WPF desktop application](../getting-started/walkthrough-my-first-wpf-desktop-application.md)
|
||||
- [How to: Create a New WPF Browser Application Project](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/bb628663(v=vs.100))
|
||||
- [Determine the Installed Version of WPF (.NET Framework 3.5)](https://docs.microsoft.com/previous-versions/dotnet/netframework-3.5/aa349641(v=vs.90))
|
||||
- [How to: Create a New WPF Browser Application Project](/previous-versions/visualstudio/visual-studio-2010/bb628663(v=vs.100))
|
||||
- [Determine the Installed Version of WPF (.NET Framework 3.5)](/previous-versions/dotnet/netframework-3.5/aa349641(v=vs.90))
|
||||
|
||||
+19
-1
@@ -12,7 +12,9 @@ ms.assetid: 12cadca0-b32c-4064-9a56-e6a306dcc76d
|
||||
After Windows Presentation Foundation (WPF) applications are built, they need to be deployed. Windows and the .NET Framework include several deployment technologies. The deployment technology that is used to deploy a WPF application depends on the application type. This topic provides a brief overview of each deployment technology, and how they are used in conjunction with the deployment requirements of each WPF application type.
|
||||
|
||||
<a name="Deployment_Technologies"></a>
|
||||
|
||||
## Deployment Technologies
|
||||
|
||||
Windows and the .NET Framework include several deployment technologies, including:
|
||||
|
||||
- XCopy deployment.
|
||||
@@ -22,7 +24,9 @@ After Windows Presentation Foundation (WPF) applications are built, they need to
|
||||
- ClickOnce deployment.
|
||||
|
||||
<a name="XCopy_Deployment"></a>
|
||||
|
||||
### XCopy Deployment
|
||||
|
||||
XCopy deployment refers to the use of the XCopy command-line program to copy files from one location to another. XCopy deployment is suitable under the following circumstances:
|
||||
|
||||
- The application is self-contained. It does not need to update the client to run.
|
||||
@@ -34,7 +38,9 @@ After Windows Presentation Foundation (WPF) applications are built, they need to
|
||||
Although XCopy is suitable for simple deployment scenarios, it is limited when more complex deployment capabilities are required. In particular, using XCopy often incurs the overhead for creating, executing, and maintaining scripts for managing deployment in a robust way. Furthermore, XCopy does not support versioning, uninstallation, or rollback.
|
||||
|
||||
<a name="Windows_Installer"></a>
|
||||
|
||||
### Windows Installer
|
||||
|
||||
Windows Installer allows applications to be packaged as self-contained executables that can be easily distributed to clients and run. Furthermore, Windows Installer is installed with Windows and enables integration with the desktop, the Start menu, and the Programs control panel.
|
||||
|
||||
Windows Installer simplifies the installation and uninstallation of applications, but it does not provide facilities for ensuring that installed applications are kept up-to-date from a versioning standpoint.
|
||||
@@ -42,7 +48,9 @@ After Windows Presentation Foundation (WPF) applications are built, they need to
|
||||
For more information about Windows Installer, see [Windows Installer Deployment](/visualstudio/deployment/deploying-applications-services-and-components#create-an-installer-package-windows-desktop).
|
||||
|
||||
<a name="ClickOnce_Deployment"></a>
|
||||
|
||||
### ClickOnce Deployment
|
||||
|
||||
ClickOnce enables Web-style application deployment for non-Web applications. Applications are published to and deployed from Web or file servers. Although ClickOnce does not support the full range of client features that Windows Installer-installed applications do, it does support a subset that includes the following:
|
||||
|
||||
- Integration with the Start menu and Programs control panel.
|
||||
@@ -58,7 +66,9 @@ After Windows Presentation Foundation (WPF) applications are built, they need to
|
||||
For more information about ClickOnce, see [ClickOnce Security and Deployment](/visualstudio/deployment/clickonce-security-and-deployment).
|
||||
|
||||
<a name="Deploying_WPF_Applications"></a>
|
||||
|
||||
## Deploying WPF Applications
|
||||
|
||||
The deployment options for a WPF application depend on the type of application. From a deployment perspective, WPF has three significant application types:
|
||||
|
||||
- Standalone applications.
|
||||
@@ -68,11 +78,15 @@ After Windows Presentation Foundation (WPF) applications are built, they need to
|
||||
- XAML browser applications (XBAPs).
|
||||
|
||||
<a name="Deploying_Standalone_Applications"></a>
|
||||
|
||||
### Deploying Standalone Applications
|
||||
|
||||
Standalone applications are deployed using either ClickOnce or Windows Installer. Either way, standalone applications require full trust to run. Full trust is automatically granted to standalone applications that are deployed using Windows Installer. Standalone applications that are deployed using ClickOnce are not automatically granted full trust. Instead, ClickOnce displays a security warning dialog that users must accept before a standalone application is installed. If accepted, the standalone application is installed and granted full trust. If not, the standalone application is not installed.
|
||||
|
||||
<a name="Deploying_Markup_Only_XAML_Applications"></a>
|
||||
|
||||
### Deploying Markup-Only XAML Applications
|
||||
|
||||
Markup-only [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] pages are usually published to Web servers, like HTML pages, and can be viewed using Internet Explorer. Markup-only [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] pages run within a partial-trust security sandbox with restrictions that are defined by the Internet zone permission set. This provides an equivalent security sandbox to HTML-based Web applications.
|
||||
|
||||
For more information about security for WPF applications, see [Security](../security-wpf.md).
|
||||
@@ -82,7 +96,9 @@ After Windows Presentation Foundation (WPF) applications are built, they need to
|
||||
For more information about XAML, see [XAML Overview (WPF)](/dotnet/desktop-wpf/fundamentals/xaml).
|
||||
|
||||
<a name="Deploying_XAML_Browser_Applications"></a>
|
||||
|
||||
### Deploying XAML Browser Applications
|
||||
|
||||
XBAPs are compiled applications that require the following three files to be deployed:
|
||||
|
||||
- *ApplicationName*.exe: The executable assembly application file.
|
||||
@@ -94,7 +110,7 @@ After Windows Presentation Foundation (WPF) applications are built, they need to
|
||||
> [!NOTE]
|
||||
> For more information about deployment and application manifests, see [Building a WPF Application](building-a-wpf-application-wpf.md).
|
||||
|
||||
These files are produced when an XBAP is built. For more information, see [How to: Create a New WPF Browser Application Project](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/bb628663(v=vs.100)). Like markup-only [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] pages, XBAPs are typically published to a Web server and viewed using Internet Explorer.
|
||||
These files are produced when an XBAP is built. For more information, see [How to: Create a New WPF Browser Application Project](/previous-versions/visualstudio/visual-studio-2010/bb628663(v=vs.100)). Like markup-only [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] pages, XBAPs are typically published to a Web server and viewed using Internet Explorer.
|
||||
|
||||
XBAPs can be deployed to clients using any of the deployment techniques. However, ClickOnce is recommended since it provides the following capabilities:
|
||||
|
||||
@@ -107,7 +123,9 @@ After Windows Presentation Foundation (WPF) applications are built, they need to
|
||||
For more information about deploying XAML browser applications (XBAPs), see [WPF XAML Browser Applications Overview](wpf-xaml-browser-applications-overview.md).
|
||||
|
||||
<a name="Installing__NET_Framework_3_0"></a>
|
||||
|
||||
## Installing the .NET Framework
|
||||
|
||||
To run a WPF application, the Microsoft .NET Framework must be installed on the client. Internet Explorer automatically detects whether clients are installed with .NET Framework when WPF browser-hosted applications are viewed. If the .NET Framework is not installed, Internet Explorer prompts users to install it.
|
||||
|
||||
To detect whether the .NET Framework is installed, Internet Explorer includes a bootstrapper application that is registered as the fallback Multipurpose Internet Mail Extensions (MIME) handler for content files with the following extensions: .xaml, .xps, .xbap, and .application. If you navigate to these file types and the .NET Framework is not installed on the client, the bootstrapper application requests permission to install it. If permission is not provided, neither the .NET Framework nor the application is installed.
|
||||
|
||||
+1
-1
@@ -42,4 +42,4 @@ In **Solution Explorer**, delete the splash screen image.
|
||||
## See also
|
||||
|
||||
- <xref:System.Windows.SplashScreen>
|
||||
- [How to: Add Existing Items to a Project](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/9f4t9t92(v=vs.100))
|
||||
- [How to: Add Existing Items to a Project](/previous-versions/visualstudio/visual-studio-2010/9f4t9t92(v=vs.100))
|
||||
|
||||
+11
-2
@@ -14,6 +14,7 @@ helpviewer_keywords:
|
||||
ms.assetid: 86375525-282b-4039-8352-8680051a10ea
|
||||
---
|
||||
# How to: Create an Add-In That Is a UI
|
||||
|
||||
This example shows how to create an add-in that is a Windows Presentation Foundation (WPF) which is hosted by a WPF standalone application.
|
||||
|
||||
The add-in is a UI that is a WPF user control. The content of the user control is a single button that, when clicked, displays a message box. The WPF standalone application hosts the add-in UI as the content of the main application window.
|
||||
@@ -22,14 +23,16 @@ This example shows how to create an add-in that is a Windows Presentation Founda
|
||||
|
||||
This example highlights the WPF extensions to the .NET Framework add-in model that enable this scenario, and assumes the following:
|
||||
|
||||
- Knowledge of the .NET Framework add-in model, including pipeline, add-in, and host development. If you are unfamiliar with these concepts, see [Add-ins and Extensibility](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb384200(v%3dvs.100)). For a tutorial that demonstrates the implementation of a pipeline, an add-in, and a host application, see [Walkthrough: Creating an Extensible Application](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb788290(v%3dvs.100)).
|
||||
- Knowledge of the .NET Framework add-in model, including pipeline, add-in, and host development. If you are unfamiliar with these concepts, see [Add-ins and Extensibility](/previous-versions/dotnet/netframework-4.0/bb384200(v%3dvs.100)). For a tutorial that demonstrates the implementation of a pipeline, an add-in, and a host application, see [Walkthrough: Creating an Extensible Application](/previous-versions/dotnet/netframework-4.0/bb788290(v%3dvs.100)).
|
||||
|
||||
- Knowledge of the WPF extensions to the .NET Framework add-in model. See [WPF Add-Ins Overview](wpf-add-ins-overview.md).
|
||||
|
||||
## Example
|
||||
|
||||
To create an add-in that is a WPF UI requires specific code for each pipeline segment, the add-in, and the host application.
|
||||
|
||||
<a name="Contract"></a>
|
||||
|
||||
## Implementing the Contract Pipeline Segment
|
||||
|
||||
When an add-in is a UI, the contract for the add-in must implement <xref:System.AddIn.Contract.INativeHandleContract>. In the example, `IWPFAddInContract` implements <xref:System.AddIn.Contract.INativeHandleContract>, as shown in the following code.
|
||||
@@ -38,6 +41,7 @@ When an add-in is a UI, the contract for the add-in must implement <xref:System.
|
||||
[!code-vb[SimpleAddInIsAUISample#ContractCode](~/samples/snippets/visualbasic/VS_Snippets_Wpf/SimpleAddInIsAUISample/VisualBasic/Contracts/IWPFAddInContract.vb#contractcode)]
|
||||
|
||||
<a name="AddInViewPipeline"></a>
|
||||
|
||||
## Implementing the Add-In View Pipeline Segment
|
||||
|
||||
Because the add-in is implemented as a subclass of the <xref:System.Windows.FrameworkElement> type, the add-in view must also subclass <xref:System.Windows.FrameworkElement>. The following code shows the add-in view of the contract, implemented as the `WPFAddInView` class.
|
||||
@@ -48,6 +52,7 @@ Because the add-in is implemented as a subclass of the <xref:System.Windows.Fram
|
||||
Here, the add-in view is derived from <xref:System.Windows.Controls.UserControl>. Consequently, the add-in UI should also derive from <xref:System.Windows.Controls.UserControl>.
|
||||
|
||||
<a name="AddInSideAdapter"></a>
|
||||
|
||||
## Implementing the Add-In-Side Adapter Pipeline Segment
|
||||
|
||||
While the contract is an <xref:System.AddIn.Contract.INativeHandleContract>, the add-in is a <xref:System.Windows.FrameworkElement> (as specified by the add-in view pipeline segment). Therefore, the <xref:System.Windows.FrameworkElement> must be converted to an <xref:System.AddIn.Contract.INativeHandleContract> before crossing the isolation boundary. This work is performed by the add-in-side adapter by calling <xref:System.AddIn.Pipeline.FrameworkElementAdapters.ViewToContractAdapter%2A>, as shown in the following code.
|
||||
@@ -63,6 +68,7 @@ In the add-in model where an add-in returns a UI (see [Create an Add-In That Ret
|
||||
Because the add-in-side adapter implements an interface that derives from <xref:System.AddIn.Contract.INativeHandleContract>, you also need to implement <xref:System.AddIn.Contract.INativeHandleContract.GetHandle%2A>, although this is ignored when <xref:System.AddIn.Pipeline.ContractBase.QueryContract%2A> is overridden.
|
||||
|
||||
<a name="HostViewPipeline"></a>
|
||||
|
||||
## Implementing the Host View Pipeline Segment
|
||||
|
||||
In this model, the host application typically expects the host view to be a <xref:System.Windows.FrameworkElement> subclass. The host-side adapter must convert the <xref:System.AddIn.Contract.INativeHandleContract> to a <xref:System.Windows.FrameworkElement> after the <xref:System.AddIn.Contract.INativeHandleContract> crosses the isolation boundary. Because a method isn't being called by the host application to get the <xref:System.Windows.FrameworkElement>, the host view must "return" the <xref:System.Windows.FrameworkElement> by containing it. Consequently, the host view must derive from a subclass of <xref:System.Windows.FrameworkElement> that can contain other UIs, such as <xref:System.Windows.Controls.UserControl>. The following code shows the host view of the contract, implemented as the `WPFAddInHostView` class.
|
||||
@@ -71,6 +77,7 @@ In this model, the host application typically expects the host view to be a <xre
|
||||
[!code-vb[WPFAddInHostView class](~/samples/snippets/visualbasic/VS_Snippets_Wpf/SimpleAddInIsAUISample/VisualBasic/HostViews/WPFAddInHostView.vb#HostViewCode)]
|
||||
|
||||
<a name="HostSideAdapter"></a>
|
||||
|
||||
## Implementing the Host-Side Adapter Pipeline Segment
|
||||
|
||||
While the contract is an <xref:System.AddIn.Contract.INativeHandleContract>, the host application expects a <xref:System.Windows.Controls.UserControl> (as specified by the host view). Consequently, the <xref:System.AddIn.Contract.INativeHandleContract> must be converted to a <xref:System.Windows.FrameworkElement> after crossing the isolation boundary, before being set as content of the host view (which derives from <xref:System.Windows.Controls.UserControl>).
|
||||
@@ -85,6 +92,7 @@ As you can see, the host-side adapter acquires the <xref:System.AddIn.Contract.I
|
||||
The host-side adapter then converts the <xref:System.AddIn.Contract.INativeHandleContract> to a <xref:System.Windows.FrameworkElement> by calling <xref:System.AddIn.Pipeline.FrameworkElementAdapters.ContractToViewAdapter%2A>. Finally, the <xref:System.Windows.FrameworkElement> is set as the content of the host view.
|
||||
|
||||
<a name="AddIn"></a>
|
||||
|
||||
## Implementing the Add-In
|
||||
|
||||
With the add-in-side adapter and add-in view in place, the add-in can be implemented by deriving from the add-in view, as shown in the following code.
|
||||
@@ -95,6 +103,7 @@ With the add-in-side adapter and add-in view in place, the add-in can be impleme
|
||||
From this example, you can see one interesting benefit of this model: add-in developers only need to implement the add-in (since it is the UI as well), rather than both an add-in class and an add-in UI.
|
||||
|
||||
<a name="HostApp"></a>
|
||||
|
||||
## Implementing the Host Application
|
||||
|
||||
With the host-side adapter and host view created, the host application can use the .NET Framework add-in model to open the pipeline and acquire a host view of the add-in. These steps are shown in the following code.
|
||||
@@ -114,5 +123,5 @@ The host application uses typical .NET Framework add-in model code to activate t
|
||||
|
||||
## See also
|
||||
|
||||
- [Add-ins and Extensibility](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb384200(v%3dvs.100))
|
||||
- [Add-ins and Extensibility](/previous-versions/dotnet/netframework-4.0/bb384200(v%3dvs.100))
|
||||
- [WPF Add-Ins Overview](wpf-add-ins-overview.md)
|
||||
|
||||
+18
-2
@@ -11,6 +11,7 @@ helpviewer_keywords:
|
||||
ms.assetid: 57f274b7-4c66-4b72-92eb-81939a393776
|
||||
---
|
||||
# How to: Create an Add-In That Returns a UI
|
||||
|
||||
This example shows how to create an add-in that returns a Windows Presentation Foundation (WPF) to a host WPF standalone application.
|
||||
|
||||
The add-in returns a UI that is a WPF user control. The content of the user control is a single button that, when clicked, displays a message box. The WPF standalone application hosts the add-in and displays the user control (returned by the add-in) as the content of the main application window.
|
||||
@@ -19,50 +20,63 @@ This example shows how to create an add-in that returns a Windows Presentation F
|
||||
|
||||
This example highlights the WPF extensions to the .NET Framework add-in model that enable this scenario, and assumes the following:
|
||||
|
||||
- Knowledge of the .NET Framework add-in model, including pipeline, add-in, and host development. If you are unfamiliar with these concepts, see [Add-ins and Extensibility](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb384200(v%3dvs.100)). For a tutorial that demonstrates the implementation of a pipeline, an add-in, and a host application, see [Walkthrough: Creating an Extensible Application](/previous-versions/dotnet/netframework-4.0/bb788290(v%3dvs.100)).
|
||||
- Knowledge of the .NET Framework add-in model, including pipeline, add-in, and host development. If you are unfamiliar with these concepts, see [Add-ins and Extensibility](/previous-versions/dotnet/netframework-4.0/bb384200(v%3dvs.100)). For a tutorial that demonstrates the implementation of a pipeline, an add-in, and a host application, see [Walkthrough: Creating an Extensible Application](/previous-versions/dotnet/netframework-4.0/bb788290(v%3dvs.100)).
|
||||
|
||||
- Knowledge of the WPF extensions to the .NET Framework add-in model, which can be found here: [WPF Add-Ins Overview](wpf-add-ins-overview.md).
|
||||
|
||||
## Example
|
||||
|
||||
To create an add-in that returns a WPF UI requires specific code for each pipeline segment, the add-in, and the host application.
|
||||
|
||||
<a name="Contract"></a>
|
||||
|
||||
## Implementing the Contract Pipeline Segment
|
||||
|
||||
A method must be defined by the contract for returning a UI, and its return value must be of type <xref:System.AddIn.Contract.INativeHandleContract>. This is demonstrated by the `GetAddInUI` method of the `IWPFAddInContract` contract in the following code.
|
||||
|
||||
[!code-csharp[SimpleAddInReturnsAUISample#ContractCode](~/samples/snippets/csharp/VS_Snippets_Wpf/SimpleAddInReturnsAUISample/CSharp/Contracts/IWPFAddInContract.cs#contractcode)]
|
||||
[!code-vb[SimpleAddInReturnsAUISample#ContractCode](~/samples/snippets/visualbasic/VS_Snippets_Wpf/SimpleAddInReturnsAUISample/VisualBasic/Contracts/IWPFAddInContract.vb#contractcode)]
|
||||
|
||||
<a name="AddInView"></a>
|
||||
|
||||
## Implementing the Add-In View Pipeline Segment
|
||||
|
||||
Because the add-in implements the UIs it provides as subclasses of <xref:System.Windows.FrameworkElement>, the method on the add-in view that correlates to `IWPFAddInView.GetAddInUI` must return a value of type <xref:System.Windows.FrameworkElement>. The following code shows the add-in view of the contract, implemented as an interface.
|
||||
|
||||
[!code-csharp[SimpleAddInReturnsAUISample#AddInViewCode](~/samples/snippets/csharp/VS_Snippets_Wpf/SimpleAddInReturnsAUISample/CSharp/AddInViews/IWPFAddInView.cs#addinviewcode)]
|
||||
[!code-vb[SimpleAddInReturnsAUISample#AddInViewCode](~/samples/snippets/visualbasic/VS_Snippets_Wpf/SimpleAddInReturnsAUISample/VisualBasic/AddInViews/IWPFAddInView.vb#addinviewcode)]
|
||||
|
||||
<a name="AddInSideAdapter"></a>
|
||||
|
||||
## Implementing the Add-In-Side Adapter Pipeline Segment
|
||||
|
||||
The contract method returns an <xref:System.AddIn.Contract.INativeHandleContract>, but the add-in returns a <xref:System.Windows.FrameworkElement> (as specified by the add-in view). Consequently, the <xref:System.Windows.FrameworkElement> must be converted to an <xref:System.AddIn.Contract.INativeHandleContract> before crossing the isolation boundary. This work is performed by the add-in-side adapter by calling <xref:System.AddIn.Pipeline.FrameworkElementAdapters.ViewToContractAdapter%2A>, as shown in the following code.
|
||||
|
||||
[!code-csharp[SimpleAddInReturnsAUISample#AddInSideAdapterCode](~/samples/snippets/csharp/VS_Snippets_Wpf/SimpleAddInReturnsAUISample/CSharp/AddInSideAdapters/WPFAddIn_ViewToContractAddInSideAdapter.cs#addinsideadaptercode)]
|
||||
[!code-vb[SimpleAddInReturnsAUISample#AddInSideAdapterCode](~/samples/snippets/visualbasic/VS_Snippets_Wpf/SimpleAddInReturnsAUISample/VisualBasic/AddInSideAdapters/WPFAddIn_ViewToContractAddInSideAdapter.vb#addinsideadaptercode)]
|
||||
|
||||
<a name="HostView"></a>
|
||||
|
||||
## Implementing the Host View Pipeline Segment
|
||||
|
||||
Because the host application will display a <xref:System.Windows.FrameworkElement>, the method on the host view that correlates to `IWPFAddInHostView.GetAddInUI` must return a value of type <xref:System.Windows.FrameworkElement>. The following code shows the host view of the contract, implemented as an interface.
|
||||
|
||||
[!code-csharp[SimpleAddInReturnsAUISample#HostViewCode](~/samples/snippets/csharp/VS_Snippets_Wpf/SimpleAddInReturnsAUISample/CSharp/HostViews/IWPFAddInHostView.cs#hostviewcode)]
|
||||
[!code-vb[SimpleAddInReturnsAUISample#HostViewCode](~/samples/snippets/visualbasic/VS_Snippets_Wpf/SimpleAddInReturnsAUISample/VisualBasic/HostViews/IWPFAddInHostView.vb#hostviewcode)]
|
||||
|
||||
<a name="HostSideAdapter"></a>
|
||||
|
||||
## Implementing the Host-Side Adapter Pipeline Segment
|
||||
|
||||
The contract method returns an <xref:System.AddIn.Contract.INativeHandleContract>, but the host application expects a <xref:System.Windows.FrameworkElement> (as specified by the host view). Consequently, the <xref:System.AddIn.Contract.INativeHandleContract> must be converted to a <xref:System.Windows.FrameworkElement> after crossing the isolation boundary. This work is performed by the host-side adapter by calling <xref:System.AddIn.Pipeline.FrameworkElementAdapters.ContractToViewAdapter%2A>, as shown in the following code.
|
||||
|
||||
[!code-csharp[SimpleAddInReturnsAUISample#HostSideAdapterCode](~/samples/snippets/csharp/VS_Snippets_Wpf/SimpleAddInReturnsAUISample/CSharp/HostSideAdapters/WPFAddIn_ContractToViewHostSideAdapter.cs#hostsideadaptercode)]
|
||||
[!code-vb[SimpleAddInReturnsAUISample#HostSideAdapterCode](~/samples/snippets/visualbasic/VS_Snippets_Wpf/SimpleAddInReturnsAUISample/VisualBasic/HostSideAdapters/WPFAddIn_ContractToViewHostSideAdapter.vb#hostsideadaptercode)]
|
||||
|
||||
<a name="AddIn"></a>
|
||||
|
||||
## Implementing the Add-In
|
||||
|
||||
With the add-in-side adapter and add-in view created, the add-in (`WPFAddIn1.AddIn`) must implement the `IWPFAddInView.GetAddInUI` method to return a <xref:System.Windows.FrameworkElement> object (a <xref:System.Windows.Controls.UserControl> in this example). The implementation of the <xref:System.Windows.Controls.UserControl>, `AddInUI`, is shown by the following code.
|
||||
|
||||
[!code-xaml[SimpleAddInReturnsAUISample#AddInUIMarkup](~/samples/snippets/csharp/VS_Snippets_Wpf/SimpleAddInReturnsAUISample/CSharp/WPFAddIn1/AddInUI.xaml#addinuimarkup)]
|
||||
@@ -76,7 +90,9 @@ This example shows how to create an add-in that returns a Windows Presentation F
|
||||
[!code-vb[SimpleAddInReturnsAUISample#AddInCode](~/samples/snippets/visualbasic/VS_Snippets_Wpf/SimpleAddInReturnsAUISample/VisualBasic/WPFAddIn1/AddIn.vb#addincode)]
|
||||
|
||||
<a name="App"></a>
|
||||
|
||||
## Implementing the Host Application
|
||||
|
||||
With the host-side adapter and host view created, the host application can use the .NET Framework add-in model to open the pipeline, acquire a host view of the add-in, and call the `IWPFAddInHostView.GetAddInUI` method. These steps are shown in the following code.
|
||||
|
||||
[!code-csharp[SimpleAddInReturnsAUISample#GetUICode](~/samples/snippets/csharp/VS_Snippets_Wpf/SimpleAddInReturnsAUISample/CSharp/Host/MainWindow.xaml.cs#getuicode)]
|
||||
@@ -84,5 +100,5 @@ This example shows how to create an add-in that returns a Windows Presentation F
|
||||
|
||||
## See also
|
||||
|
||||
- [Add-ins and Extensibility](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb384200(v%3dvs.100))
|
||||
- [Add-ins and Extensibility](/previous-versions/dotnet/netframework-4.0/bb384200(v%3dvs.100))
|
||||
- [WPF Add-Ins Overview](wpf-add-ins-overview.md)
|
||||
|
||||
+4
-1
@@ -8,13 +8,16 @@ helpviewer_keywords:
|
||||
ms.assetid: 7f71d652-1749-4379-945a-aa2e3994cb43
|
||||
---
|
||||
# How to: Detect Whether the .NET Framework 3.0 Is Installed
|
||||
|
||||
Before administrators can deploy Microsoft .NET Framework applications on a system, they must first confirm that the .NET Framework runtime is present. This topic provides a script written in HTML/JavaScript that administrators can use to determine whether the .NET Framework is present on a system.
|
||||
|
||||
> [!NOTE]
|
||||
> For more detailed information on installing, deploying, and detecting the Microsoft .NET Framework, see the discussion in [Deploying Microsoft .NET Framework Version 3.0](https://docs.microsoft.com/previous-versions/dotnet/articles/aa480198(v=msdn.10)).
|
||||
> For more detailed information on installing, deploying, and detecting the Microsoft .NET Framework, see the discussion in [Deploying Microsoft .NET Framework Version 3.0](/previous-versions/dotnet/articles/aa480198(v=msdn.10)).
|
||||
|
||||
<a name="content_expiration"></a>
|
||||
|
||||
## Detect the ".NET CLR" User-Agent String
|
||||
|
||||
When .NET Framework is installed, the MSI adds ".NET CLR" and the version number to the UserAgent string. The following example shows a script embedded in a simple HTML page. The script searches the UserAgent string to determine whether .NET Framework is installed, and displays a status message on the results of the search.
|
||||
|
||||
```html
|
||||
|
||||
+3
-1
@@ -12,10 +12,12 @@ helpviewer_keywords:
|
||||
ms.assetid: 53857682-bd2c-4f2c-8f25-1307d0b451a2
|
||||
---
|
||||
# How to: Use an Application-Scope Resource Dictionary
|
||||
|
||||
This example shows how to define and use an application-scope custom resource dictionary.
|
||||
|
||||
## Example
|
||||
<xref:System.Windows.Application> exposes an application-scope store for shared resources: <xref:System.Windows.Application.Resources%2A>. By default, the <xref:System.Windows.Application.Resources%2A> property is initialized with an instance of the <xref:System.Windows.ResourceDictionary> type. You use this instance when you get and set application-scope properties using <xref:System.Windows.Application.Resources%2A>. For more information, see [How to: Get and Set an Application-Scope Resource](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/aa348547(v=vs.100)).
|
||||
|
||||
<xref:System.Windows.Application> exposes an application-scope store for shared resources: <xref:System.Windows.Application.Resources%2A>. By default, the <xref:System.Windows.Application.Resources%2A> property is initialized with an instance of the <xref:System.Windows.ResourceDictionary> type. You use this instance when you get and set application-scope properties using <xref:System.Windows.Application.Resources%2A>. For more information, see [How to: Get and Set an Application-Scope Resource](/previous-versions/dotnet/netframework-4.0/aa348547(v=vs.100)).
|
||||
|
||||
If you have multiple resources that you set using <xref:System.Windows.Application.Resources%2A>, you can instead use a custom resource dictionary to store those resources and set <xref:System.Windows.Application.Resources%2A> with it instead. The following shows how you declare a custom resource dictionary using XAML.
|
||||
|
||||
|
||||
@@ -6,10 +6,12 @@ helpviewer_keywords:
|
||||
ms.assetid: cc5a0281-de81-4cc1-87e4-0e46b1a811e9
|
||||
---
|
||||
# IWpfHostSupport
|
||||
|
||||
Applications that host [!INCLUDE[TLA#tla_winclient](../../../includes/tlasharptla-winclient-md.md)] content via PresentationHost.exe implement this interface to provide a point of integration between the host and PresentationHost.exe.
|
||||
|
||||
## Remarks
|
||||
Win32 applications such as Web browsers can host WPF content, including XAML browser applications (XBAPs) and loose XAML. To host WPF content, Win32 applications create an instance of the [WebBrowser control](https://docs.microsoft.com/previous-versions/windows/internet-explorer/ie-developer/platform-apis/aa752040(v=vs.85)). To be hosted, WPF creates an instance of PresentationHost.exe, which provides the hosted WPF content to the host for display in the [WebBrowser control](https://docs.microsoft.com/previous-versions/windows/internet-explorer/ie-developer/platform-apis/aa752040(v=vs.85)).
|
||||
|
||||
Win32 applications such as Web browsers can host WPF content, including XAML browser applications (XBAPs) and loose XAML. To host WPF content, Win32 applications create an instance of the [WebBrowser control](/previous-versions/windows/internet-explorer/ie-developer/platform-apis/aa752040(v=vs.85)). To be hosted, WPF creates an instance of PresentationHost.exe, which provides the hosted WPF content to the host for display in the [WebBrowser control](/previous-versions/windows/internet-explorer/ie-developer/platform-apis/aa752040(v=vs.85)).
|
||||
|
||||
The integration enabled by `IWpfHostSupport` allows PresentationHost.exe to:
|
||||
|
||||
|
||||
+4
-1
@@ -9,11 +9,13 @@ helpviewer_keywords:
|
||||
ms.assetid: 82c133a8-d760-45fb-a2b9-3a997537f1d4
|
||||
---
|
||||
# Native WPF Browser Hosting Support APIs
|
||||
|
||||
Hosting of WPF applications in Web browsers is facilitated by an Active Document server (also known as a DocObject) registered out of the WPF Host. Internet Explorer can directly activate and integrate with an Active Document. For hosting of XBAPs and loose XAML documents in Mozilla browsers, WPF provides an NPAPI plugin, which provides a similar hosting environment to the WPF Active Document server as Internet Explorer does. However, the easiest practical way to host XBAPs and XAML documents in other browsers and standalone applications is via the Internet Explorer Web Browser control. The Web Browser control provides the complex Active Document server hosting environment, yet it enables its own host to customize and extend that environment and communicate directly with the current Active Document object.
|
||||
|
||||
The WPF Active Document server implements several common hosting interfaces, including [IOleObject](/windows/win32/api/oleidl/nn-oleidl-ioleobject), [IOleDocument](/windows/win32/api/docobj/nn-docobj-ioledocument), [IOleInPlaceActiveObject](/windows/win32/api/oleidl/nn-oleidl-ioleinplaceactiveobject), [IPersistMoniker](https://docs.microsoft.com/previous-versions/windows/internet-explorer/ie-developer/platform-apis/ms775042(v=vs.85)), [IOleCommandTarget](/windows/win32/api/docobj/nn-docobj-iolecommandtarget). When hosted in the Web Browser control, these interfaces can be queries from the object returned by the [IWebBrowser2::Document](https://docs.microsoft.com/previous-versions/aa752116(v=vs.85)) property.
|
||||
The WPF Active Document server implements several common hosting interfaces, including [IOleObject](/windows/win32/api/oleidl/nn-oleidl-ioleobject), [IOleDocument](/windows/win32/api/docobj/nn-docobj-ioledocument), [IOleInPlaceActiveObject](/windows/win32/api/oleidl/nn-oleidl-ioleinplaceactiveobject), [IPersistMoniker](/previous-versions/windows/internet-explorer/ie-developer/platform-apis/ms775042(v=vs.85)), [IOleCommandTarget](/windows/win32/api/docobj/nn-docobj-iolecommandtarget). When hosted in the Web Browser control, these interfaces can be queries from the object returned by the [IWebBrowser2::Document](/previous-versions/aa752116(v=vs.85)) property.
|
||||
|
||||
## IOleCommandTarget
|
||||
|
||||
WPF Active Document server's implementation of [IOleCommandTarget](/windows/win32/api/docobj/nn-docobj-iolecommandtarget) supports numerous navigation-related and browser-specific commands of the standard OLE command group (with a null command group GUID). In addition, it recognizes a custom command group called CGID_PresentationHost. Currently, there is only one command defined within this group.
|
||||
|
||||
```cpp
|
||||
@@ -26,5 +28,6 @@ enum PresentationHostCommands {
|
||||
PHCMDID_TABINTO instructs PresentationHost to switch focus to the first or last focusable element in its content, depending on the state of the Shift key.
|
||||
|
||||
## In This Section
|
||||
|
||||
[IEnumRAWINPUTDEVICE](ienumrawinputdevice.md)
|
||||
[IWpfHostSupport](iwpfhostsupport.md)
|
||||
|
||||
@@ -21,7 +21,7 @@ ms.assetid: 00b4c776-29a8-4dba-b603-280a0cdc2ade
|
||||
|
||||
## Prerequisites
|
||||
|
||||
Familiarity with the .NET Framework add-in model is required. For more information, see [Add-ins and Extensibility](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb384200(v%3dvs.100)).
|
||||
Familiarity with the .NET Framework add-in model is required. For more information, see [Add-ins and Extensibility](/previous-versions/dotnet/netframework-4.0/bb384200(v%3dvs.100)).
|
||||
|
||||
<a name="AddInsOverview"></a>
|
||||
|
||||
@@ -60,7 +60,7 @@ In order for add-ins to be used, host applications need to find them and load th
|
||||
Ultimately, developing a robust add-in model is a non-trivial undertaking. For this reason, the .NET Framework provides an infrastructure for building add-in models.
|
||||
|
||||
> [!NOTE]
|
||||
> For more detailed information on add-ins, see [Add-ins and Extensibility](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb384200(v%3dvs.100)).
|
||||
> For more detailed information on add-ins, see [Add-ins and Extensibility](/previous-versions/dotnet/netframework-4.0/bb384200(v%3dvs.100)).
|
||||
|
||||
<a name="NETFrameworkAddInModelOverview"></a>
|
||||
|
||||
@@ -101,7 +101,7 @@ A remotable object is an instance of a class that does one or more of the follow
|
||||
- Has the <xref:System.SerializableAttribute> attribute applied.
|
||||
|
||||
> [!NOTE]
|
||||
> For more information regarding the creation of remotable .NET Framework objects, see [Making Objects Remotable](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/wcf3swha(v=vs.100)).
|
||||
> For more information regarding the creation of remotable .NET Framework objects, see [Making Objects Remotable](/previous-versions/dotnet/netframework-4.0/wcf3swha(v=vs.100)).
|
||||
|
||||
The WPF UI types are not remotable. To solve the problem, WPF extends the .NET Framework add-in model to enable WPF UI created by add-ins to be displayed from host applications. This support is provided by WPF by two types: the <xref:System.AddIn.Contract.INativeHandleContract> interface and two static methods implemented by the <xref:System.AddIn.Pipeline.FrameworkElementAdapters> class: <xref:System.AddIn.Pipeline.FrameworkElementAdapters.ContractToViewAdapter%2A> and <xref:System.AddIn.Pipeline.FrameworkElementAdapters.ViewToContractAdapter%2A>. At a high level, these types and methods are used in the following manner:
|
||||
|
||||
@@ -121,7 +121,7 @@ How <xref:System.AddIn.Contract.INativeHandleContract>, <xref:System.AddIn.Pipel
|
||||
|
||||
For an add-in to return a UI to a host application, the following are required:
|
||||
|
||||
1. The host application, add-in, and pipeline must be created, as described by the .NET Framework [Add-ins and Extensibility](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb384200(v%3dvs.100)) documentation.
|
||||
1. The host application, add-in, and pipeline must be created, as described by the .NET Framework [Add-ins and Extensibility](/previous-versions/dotnet/netframework-4.0/bb384200(v%3dvs.100)) documentation.
|
||||
|
||||
2. The contract must implement <xref:System.AddIn.Contract.IContract> and, to return a UI, the contract must declare a method with a return value of type <xref:System.AddIn.Contract.INativeHandleContract>.
|
||||
|
||||
@@ -141,7 +141,7 @@ For an example that demonstrates how to implement an add-in that returns a UI, s
|
||||
|
||||
When an add-in is a UI, the following are required:
|
||||
|
||||
1. The host application, add-in, and pipeline must be created, as described by the .NET Framework [Add-ins and Extensibility](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb384200(v%3dvs.100)) documentation.
|
||||
1. The host application, add-in, and pipeline must be created, as described by the .NET Framework [Add-ins and Extensibility](/previous-versions/dotnet/netframework-4.0/bb384200(v%3dvs.100)) documentation.
|
||||
|
||||
2. The contract interface for the add-in must implement <xref:System.AddIn.Contract.INativeHandleContract>.
|
||||
|
||||
@@ -305,8 +305,8 @@ By default, when multiple application domains are used, the various .NET Framewo
|
||||
## See also
|
||||
|
||||
- <xref:System.LoaderOptimizationAttribute>
|
||||
- [Add-ins and Extensibility](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/bb384200(v%3dvs.100))
|
||||
- [Add-ins and Extensibility](/previous-versions/dotnet/netframework-4.0/bb384200(v%3dvs.100))
|
||||
- [Application Domains](/dotnet/framework/app-domains/application-domains)
|
||||
- [.NET Framework Remoting Overview](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/kwdt6w2k(v=vs.100))
|
||||
- [Making Objects Remotable](https://docs.microsoft.com/previous-versions/dotnet/netframework-4.0/wcf3swha(v=vs.100))
|
||||
- [.NET Framework Remoting Overview](/previous-versions/dotnet/netframework-4.0/kwdt6w2k(v=vs.100))
|
||||
- [Making Objects Remotable](/previous-versions/dotnet/netframework-4.0/wcf3swha(v=vs.100))
|
||||
- [How-to Topics](how-to-topics.md)
|
||||
|
||||
+17
-2
@@ -13,6 +13,7 @@ helpviewer_keywords:
|
||||
ms.assetid: 3a7a86a8-75d5-4898-96b9-73da151e5e16
|
||||
---
|
||||
# WPF XAML Browser Applications Overview
|
||||
|
||||
<a name="introduction"></a>
|
||||
XAML browser applications (XBAPs) combines features of both Web applications and rich-client applications. Like Web applications, XBAPs can be deployed to a Web server and started from Internet Explorer or Firefox. Like rich-client applications, XBAPs can take advantage of the capabilities of WPF. Developing XBAPs is also similar to rich-client development. This topic provides a simple, high-level introduction to XBAP development and describes where XBAP development differs from standard rich-client development.
|
||||
|
||||
@@ -29,8 +30,10 @@ XAML browser applications (XBAPs) combines features of both Web applications and
|
||||
- [XBAP Start Time Performance Considerations](#xbap_start_time_performance_considerations)
|
||||
|
||||
<a name="creating_a_new_xaml_browser_application_xbap"></a>
|
||||
|
||||
## Creating a New XAML Browser Application (XBAP)
|
||||
The simplest way to create a new XBAP project is with Visual Studio. When creating a new project, select **WPF Browser Application** from the list of templates. For more information, see [How to: Create a New WPF Browser Application Project](https://docs.microsoft.com/previous-versions/visualstudio/visual-studio-2010/bb628663(v=vs.100)).
|
||||
|
||||
The simplest way to create a new XBAP project is with Visual Studio. When creating a new project, select **WPF Browser Application** from the list of templates. For more information, see [How to: Create a New WPF Browser Application Project](/previous-versions/visualstudio/visual-studio-2010/bb628663(v=vs.100)).
|
||||
|
||||
When you run the XBAP project, it opens in a browser window instead of a stand-alone window. When you debug the XBAP from Visual Studio, the application runs with Internet zone permission and will therefore throw security exceptions if those permissions are exceeded. For more information, see [Security](../security-wpf.md) and [WPF Partial Trust Security](../wpf-partial-trust-security.md).
|
||||
|
||||
@@ -38,7 +41,9 @@ XAML browser applications (XBAPs) combines features of both Web applications and
|
||||
> If you are not developing with Visual Studio or want to learn more about the project files, see [Building a WPF Application](building-a-wpf-application-wpf.md).
|
||||
|
||||
<a name="deploying_a_xbap"></a>
|
||||
|
||||
## Deploying an XBAP
|
||||
|
||||
When you build an XBAP, the output includes the following three files:
|
||||
|
||||
|File|Description|
|
||||
@@ -75,6 +80,7 @@ XAML browser applications (XBAPs) combines features of both Web applications and
|
||||
```
|
||||
|
||||
### Clearing Cached XBAPs
|
||||
|
||||
In some situations after rebuilding and starting your XBAP, you may find that an earlier version of the XBAP is opened. For example, this behavior may occur when your XBAP assembly version number is static and you start the XBAP from the command line. In this case, because the version number between the cached version (the version that was previously started) and the new version remains the same, the new version of the XBAP is not downloaded. Instead, the cached version is loaded.
|
||||
|
||||
In these situations, you can remove the cached version by using the **Mage** command (installed with Visual Studio or the Windows SDK) at the command prompt. The following command clears the application cache.
|
||||
@@ -86,13 +92,16 @@ XAML browser applications (XBAPs) combines features of both Web applications and
|
||||
This command guarantees that the latest version of your XBAP is started. When you debug your application in Visual Studio, the latest version of your XBAP should be started. In general, you should update your deployment version number with each build. For more information about Mage, see [Mage.exe (Manifest Generation and Editing Tool)](/dotnet/framework/tools/mage-exe-manifest-generation-and-editing-tool).
|
||||
|
||||
<a name="communicating_with_the_host_web_page"></a>
|
||||
|
||||
## Communicating with the Host Web Page
|
||||
|
||||
When the application is hosted in an HTML frame, you can communicate with the Web page that contains the XBAP. You do this by retrieving the <xref:System.Windows.Interop.BrowserInteropHelper.HostScript%2A> property of <xref:System.Windows.Interop.BrowserInteropHelper>. This property returns a script object that represents the HTML window. You can then access the properties, methods, and events on the [window object](https://developer.mozilla.org/en-US/docs/Web/API/Window) by using regular dot syntax. You can also access script methods and global variables. The following example shows how to retrieve the script object and close the browser.
|
||||
|
||||
[!code-csharp[XbapBrowserInterop#10](~/samples/snippets/csharp/VS_Snippets_Wpf/xbapbrowserinterop/cs/page1.xaml.cs#10)]
|
||||
[!code-vb[XbapBrowserInterop#10](~/samples/snippets/visualbasic/VS_Snippets_Wpf/xbapbrowserinterop/vb/page1.xaml.vb#10)]
|
||||
|
||||
### Debugging XBAPs that Use HostScript
|
||||
|
||||
If your XBAP uses the <xref:System.Windows.Interop.BrowserInteropHelper.HostScript%2A> object to communicate with the HTML window, there are two settings that you must specify to run and debug the application in Visual Studio. The application must have access to its site of origin and you must start the application with the HTML page that contains the XBAP. The following steps describe how to check these two settings:
|
||||
|
||||
1. In Visual Studio, open the project properties.
|
||||
@@ -121,7 +130,9 @@ XAML browser applications (XBAPs) combines features of both Web applications and
|
||||
> Enabling active content in Internet Explorer may put your computer at risk. If you do not want to change your Internet Explorer security settings, you can launch the HTML page from a server and attach the Visual Studio debugger to the process.
|
||||
|
||||
<a name="xbap_security_considerations"></a>
|
||||
|
||||
## XBAP Security Considerations
|
||||
|
||||
XBAPs typically execute in a partial-trust security sandbox that is restricted to the Internet zone permission set. Consequently, your implementation must support the subset of WPF elements that are supported in the Internet zone or you must elevate the permissions of your application. For more information, see [Security](../security-wpf.md).
|
||||
|
||||
When you use a <xref:System.Windows.Controls.WebBrowser> control in your application, WPF internally instantiates the native WebBrowser ActiveX control. When your application is a partial-trust XBAP running in Internet Explorer, the ActiveX control runs in a dedicated thread of the Internet Explorer process. Therefore, the following limitations apply:
|
||||
@@ -139,6 +150,7 @@ XAML browser applications (XBAPs) combines features of both Web applications and
|
||||
- <xref:System.Windows.Interop.HwndHost.MessageHook> does not get raised because <xref:System.Windows.Interop.HwndHost> cannot subclass a window running in another thread or process.
|
||||
|
||||
### Creating a Full-Trust XBAP
|
||||
|
||||
If your XBAP requires full trust, you can change your project to enable this permission. The following steps describe how to enable full trust:
|
||||
|
||||
1. In Visual Studio, open the project properties.
|
||||
@@ -160,6 +172,7 @@ XAML browser applications (XBAPs) combines features of both Web applications and
|
||||
```
|
||||
|
||||
### Deploying a Full-Trust XBAP
|
||||
|
||||
When you deploy a full-trust XBAP that does not follow the ClickOnce Trusted Deployment model, the behavior when the user runs the application will depend on the security zone. In some cases, the user will receive a warning when they attempt to install it. The user can choose to continue or cancel the installation. The following table describes the behavior of the application for each security zone and what you have to do for the application to receive full trust.
|
||||
|
||||
|Security Zone|Behavior|Getting Full Trust|
|
||||
@@ -171,10 +184,12 @@ XAML browser applications (XBAPs) combines features of both Web applications and
|
||||
> [!NOTE]
|
||||
> The behavior described in the previous table is for full-trust XBAPs that do not follow the ClickOnce Trusted Deployment model.
|
||||
|
||||
It is recommended that you use the ClickOnce Trusted Deployment model for deploying a full-trust XBAP. This model allows your XBAP to be granted full trust automatically, regardless of the security zone, so that the user is not prompted. As part of this model, you must sign your application with a certificate from a trusted publisher. For more information, see [Trusted Application Deployment Overview](/visualstudio/deployment/trusted-application-deployment-overview) and [Introduction to Code Signing](https://docs.microsoft.com/previous-versions/windows/internet-explorer/ie-developer/platform-apis/ms537361(v=vs.85)).
|
||||
It is recommended that you use the ClickOnce Trusted Deployment model for deploying a full-trust XBAP. This model allows your XBAP to be granted full trust automatically, regardless of the security zone, so that the user is not prompted. As part of this model, you must sign your application with a certificate from a trusted publisher. For more information, see [Trusted Application Deployment Overview](/visualstudio/deployment/trusted-application-deployment-overview) and [Introduction to Code Signing](/previous-versions/windows/internet-explorer/ie-developer/platform-apis/ms537361(v=vs.85)).
|
||||
|
||||
<a name="xbap_start_time_performance_considerations"></a>
|
||||
|
||||
## XBAP Start Time Performance Considerations
|
||||
|
||||
An important aspect of XBAP performance is its start time. If an XBAP is the first WPF application to load, the *cold start* time can be ten seconds or more. This is because the progress page is rendered by WPF, and both the CLR and WPF must be cold-started to display the application.
|
||||
|
||||
Starting in .NET Framework 3.5 SP1, XBAP cold-start time is mitigated by displaying an unmanaged progress page early in the deployment cycle. The progress page appears almost immediately after the application is started, because it is displayed by native hosting code and rendered in HTML.
|
||||
|
||||
Reference in New Issue
Block a user