mirror of
https://github.com/Stone-Red-Code/docs-desktop.git
synced 2026-09-05 16:06:10 +02:00
Replace various WPF include files with content (#1335)
* net-current-v30plus-md.md * net-current-v40plus-md.md * tla2sharptla-ui-md.md * tla2sharptla-uiautomation-md.md * tla2sharptla-winclient-md.md * tla2sharptla-xaml-md.md * tlasharptla-ui-md.md * tlasharptla-uiautomation-md.md * tlasharptla-winclient-md.md * tlasharptla-xaml-md.md * fix warnings
This commit is contained in:
Andy (Steve) De George
+1
-1
@@ -10,7 +10,7 @@ ms.assetid: 88952ad2-5b74-48ca-a4c5-3f4fbb53ce12
|
||||
---
|
||||
# Build and deploy how-to topics
|
||||
|
||||
The following topics show how to create project files for the various [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] application types.
|
||||
The following topics show how to create project files for the various WPF application types.
|
||||
|
||||
## In this section
|
||||
|
||||
|
||||
+16
-16
@@ -59,17 +59,17 @@ The build process locates and binds the assemblies required to build the applica
|
||||
|
||||
### Markup Compilation—Pass 1
|
||||
|
||||
In this step, [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] files are parsed and compiled so that the runtime does not spend time parsing XML and validating property values. The compiled [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] file is pre-tokenized so that, at run time, loading it should be much faster than loading a [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] file.
|
||||
In this step, XAML files are parsed and compiled so that the runtime does not spend time parsing XML and validating property values. The compiled XAML file is pre-tokenized so that, at run time, loading it should be much faster than loading a XAML file.
|
||||
|
||||
During this step, the following activities take place for every [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] file that is a `Page` build item:
|
||||
During this step, the following activities take place for every XAML file that is a `Page` build item:
|
||||
|
||||
1. The [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] file is parsed by the markup compiler.
|
||||
1. The XAML file is parsed by the markup compiler.
|
||||
|
||||
2. A compiled representation is created for that [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] and copied to the obj\Release folder.
|
||||
2. A compiled representation is created for that XAML and copied to the obj\Release folder.
|
||||
|
||||
3. A CodeDOM representation of a new partial class is created and copied to the obj\Release folder.
|
||||
|
||||
In addition, a language-specific code file is generated for every [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] file. For example, for a Page1.xaml page in a Visual Basic project, a Page1.g.vb is generated; for a Page1.xaml page in a C# project, a Page1.g.cs is generated. The ".g" in the file name indicates the file is generated code that has a partial class declaration for the top-level element of the markup file (such as `Page` or `Window`). The class is declared with the `partial` modifier in C# (`Extends` in Visual Basic) to indicate there is another declaration for the class elsewhere, usually in the code-behind file Page1.xaml.cs.
|
||||
In addition, a language-specific code file is generated for every XAML file. For example, for a Page1.xaml page in a Visual Basic project, a Page1.g.vb is generated; for a Page1.xaml page in a C# project, a Page1.g.cs is generated. The ".g" in the file name indicates the file is generated code that has a partial class declaration for the top-level element of the markup file (such as `Page` or `Window`). The class is declared with the `partial` modifier in C# (`Extends` in Visual Basic) to indicate there is another declaration for the class elsewhere, usually in the code-behind file Page1.xaml.cs.
|
||||
|
||||
The partial class extends from the appropriate base class (such as <xref:System.Windows.Controls.Page> for a page) and implements the <xref:System.Windows.Markup.IComponentConnector?displayProperty=nameWithType> interface. The <xref:System.Windows.Markup.IComponentConnector> interface has methods to initialize a component and connect names and events on elements in its content. Consequently, the generated code file has a method implementation like the following:
|
||||
|
||||
@@ -109,13 +109,13 @@ By default, markup compilation runs in the same <xref:System.AppDomain> as the M
|
||||
|
||||
### Markup Compilation—Pass 2
|
||||
|
||||
Not all [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] pages are compiled at during pass 1 of markup compilation. [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] files that have locally defined type references (references to types defined in code elsewhere in the same project) are exempt from compilation at this time. This is because those locally defined types exist only in source and have not yet been compiled. In order to determine this, the parser uses heuristics that involve looking for items such as `x:Name` in the markup file. When such an instance is found, that markup file’s compilation is postponed until the code files have been compiled, after which, the second markup compilation pass processes these files.
|
||||
Not all XAML pages are compiled at during pass 1 of markup compilation. XAML files that have locally defined type references (references to types defined in code elsewhere in the same project) are exempt from compilation at this time. This is because those locally defined types exist only in source and have not yet been compiled. In order to determine this, the parser uses heuristics that involve looking for items such as `x:Name` in the markup file. When such an instance is found, that markup file’s compilation is postponed until the code files have been compiled, after which, the second markup compilation pass processes these files.
|
||||
|
||||
<a name="File_Classification"></a>
|
||||
|
||||
### File Classification
|
||||
|
||||
The build process puts output files into different resource groups based on which application assembly they will be placed in. In a typical nonlocalized application, all data files marked as `Resource` are placed in the main assembly (executable or library). When `UICulture` is set in the project, all compiled [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] files and those resources specifically marked as language-specific are placed in the satellite resource assembly. Furthermore, all language-neutral resources are placed in the main assembly. In this step of the build process, that determination is made.
|
||||
The build process puts output files into different resource groups based on which application assembly they will be placed in. In a typical nonlocalized application, all data files marked as `Resource` are placed in the main assembly (executable or library). When `UICulture` is set in the project, all compiled XAML files and those resources specifically marked as language-specific are placed in the satellite resource assembly. Furthermore, all language-neutral resources are placed in the main assembly. In this step of the build process, that determination is made.
|
||||
|
||||
The `ApplicationDefinition`, `Page`, and `Resource` build actions in the project file can be augmented with the `Localizable` metadata (acceptable values are `true` and `false`), which dictates whether the file is language-specific or language-neutral.
|
||||
|
||||
@@ -123,7 +123,7 @@ The `ApplicationDefinition`, `Page`, and `Resource` build actions in the project
|
||||
|
||||
### Core Compilation
|
||||
|
||||
The core compile step involves compilation of code files. This is orchestrated by logic in the language-specific targets files Microsoft.CSharp.targets and Microsoft.VisualBasic.targets. If heuristics have determined that a single pass of the markup compiler is sufficient, then the main assembly is generated. However, if one or more [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] files in the project have references to locally defined types, then a temporary .dll file is generated so the final application assemblies may be created after the second pass of markup compilation is complete.
|
||||
The core compile step involves compilation of code files. This is orchestrated by logic in the language-specific targets files Microsoft.CSharp.targets and Microsoft.VisualBasic.targets. If heuristics have determined that a single pass of the markup compiler is sufficient, then the main assembly is generated. However, if one or more XAML files in the project have references to locally defined types, then a temporary .dll file is generated so the final application assemblies may be created after the second pass of markup compilation is complete.
|
||||
|
||||
<a name="Manifest_generation"></a>
|
||||
|
||||
@@ -147,29 +147,29 @@ The WPF build system provides support for incremental builds. It is fairly intel
|
||||
|
||||
- An $(*AssemblyName*)_MarkupCompiler.Cache file to maintain current compiler state.
|
||||
|
||||
- An $(*AssemblyName*)_MarkupCompiler.lref file to cache the [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] files with references to locally defined types.
|
||||
- An $(*AssemblyName*)_MarkupCompiler.lref file to cache the XAML files with references to locally defined types.
|
||||
|
||||
The following is a set of rules governing incremental build:
|
||||
|
||||
- The file is the smallest unit at which the build system detects change. So, for a code file, the build system cannot tell if a type was changed or if code was added. The same holds for project files.
|
||||
|
||||
- The incremental build mechanism must be cognizant that a [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] page either defines a class or uses other classes.
|
||||
- The incremental build mechanism must be cognizant that a XAML page either defines a class or uses other classes.
|
||||
|
||||
- If `Reference` entries change, then recompile all pages.
|
||||
|
||||
- If a code file changes, recompile all pages with locally defined type references.
|
||||
|
||||
- If a [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] file changes:
|
||||
- If a XAML file changes:
|
||||
|
||||
- If [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] is declared as `Page` in the project: if the [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] does not have locally defined type references, recompile that [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] plus all [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] pages with local references; if the [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] has local references, recompile all [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] pages with local references.
|
||||
- If XAML is declared as `Page` in the project: if the XAML does not have locally defined type references, recompile that XAML plus all XAML pages with local references; if the XAML has local references, recompile all XAML pages with local references.
|
||||
|
||||
- If [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] is declared as `ApplicationDefinition` in the project: recompile all [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] pages (reason: each [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] has reference to an <xref:System.Windows.Application> type that may have changed).
|
||||
- If XAML is declared as `ApplicationDefinition` in the project: recompile all XAML pages (reason: each XAML has reference to an <xref:System.Windows.Application> type that may have changed).
|
||||
|
||||
- If the project file declares a code file as application definition instead of a [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] file:
|
||||
- If the project file declares a code file as application definition instead of a XAML file:
|
||||
|
||||
- Check if the `ApplicationClassName` value in the project file has changed (is there a new application type?). If so, recompile the entire application.
|
||||
|
||||
- Otherwise, recompile all [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] pages with local references.
|
||||
- Otherwise, recompile all XAML pages with local references.
|
||||
|
||||
- If a project file changes: apply all preceding rules and see what needs to be recompiled. Changes to the following properties trigger a complete recompile: `AssemblyName`, `IntermediateOutputPath`, `RootNamespace`, and `HostInBrowser`.
|
||||
|
||||
@@ -177,7 +177,7 @@ The following recompile scenarios are possible:
|
||||
|
||||
- The entire application is recompiled.
|
||||
|
||||
- Only those [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] files that have locally defined type references are recompiled.
|
||||
- Only those XAML files that have locally defined type references are recompiled.
|
||||
|
||||
- Nothing is recompiled (if nothing in the project has changed).
|
||||
|
||||
|
||||
+4
-4
@@ -74,7 +74,7 @@ After Windows Presentation Foundation (WPF) applications are built, they need to
|
||||
|
||||
- Standalone applications.
|
||||
|
||||
- Markup-only [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] applications.
|
||||
- Markup-only XAML applications.
|
||||
|
||||
- XAML browser applications (XBAPs).
|
||||
|
||||
@@ -88,11 +88,11 @@ After Windows Presentation Foundation (WPF) applications are built, they need to
|
||||
|
||||
### 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.
|
||||
Markup-only XAML pages are usually published to Web servers, like HTML pages, and can be viewed using Internet Explorer. Markup-only XAML 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).
|
||||
|
||||
Markup-only [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] pages can be installed to the local file system by using either XCopy or Windows Installer. These pages can be viewed using Internet Explorer or Windows Explorer.
|
||||
Markup-only XAML pages can be installed to the local file system by using either XCopy or Windows Installer. These pages can be viewed using Internet Explorer or Windows Explorer.
|
||||
|
||||
For more information about XAML, see [XAML in WPF](../advanced/xaml-in-wpf.md).
|
||||
|
||||
@@ -111,7 +111,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](/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 XAML 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:
|
||||
|
||||
|
||||
@@ -13,7 +13,7 @@ helpviewer_keywords:
|
||||
ms.assetid: 0d23d544-a393-4a02-a3aa-d8cd5d3d6511
|
||||
---
|
||||
# Dialog boxes overview
|
||||
Standalone applications typically have a main window that both displays the main data over which the application operates and exposes the functionality to process that data through [!INCLUDE[TLA#tla_ui](../../../includes/tlasharptla-ui-md.md)] mechanisms like menu bars, tool bars, and status bars. A non-trivial application may also display additional windows to do the following:
|
||||
Standalone applications typically have a main window that both displays the main data over which the application operates and exposes the functionality to process that data through user interface (UI) mechanisms like menu bars, tool bars, and status bars. A non-trivial application may also display additional windows to do the following:
|
||||
|
||||
- Display specific information to users.
|
||||
|
||||
|
||||
+2
-2
@@ -9,10 +9,10 @@ helpviewer_keywords:
|
||||
ms.assetid: 2403403b-9b14-48e9-b70d-fa288a3c9081
|
||||
---
|
||||
# Firefox Add-ons to Support .NET Application Deployment
|
||||
The Windows Presentation Foundation (WPF) plug-in for Firefox and the .NET Framework Assistant for Firefox enable XAML browser applications (XBAPs), loose [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)], and ClickOnce applications to work with the Mozilla Firefox browser.
|
||||
The Windows Presentation Foundation (WPF) plug-in for Firefox and the .NET Framework Assistant for Firefox enable XAML browser applications (XBAPs), loose XAML, and ClickOnce applications to work with the Mozilla Firefox browser.
|
||||
|
||||
## WPF Plug-in for Firefox
|
||||
The WPF plug-in for Firefox enables XBAPs and loose [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] files to be navigated to and run at the top-level or in an HTML IFRAME in the Firefox browser. An XBAP is a WPF application that can be published to a Web server and launched within supported browsers. Loose [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] is a XAML-only file that can be navigated to and displayed in supported browsers, much like an XML file.
|
||||
The WPF plug-in for Firefox enables XBAPs and loose XAML files to be navigated to and run at the top-level or in an HTML IFRAME in the Firefox browser. An XBAP is a WPF application that can be published to a Web server and launched within supported browsers. Loose XAML is a XAML-only file that can be navigated to and displayed in supported browsers, much like an XML file.
|
||||
|
||||
The WPF plug-in for Firefox is installed with the .NET Framework 3.5. Window 7 includes the .NET Framework 3.5, but does not include the WPF plug-in for Firefox. You cannot install the WPF plug-in for Firefox on Windows 7.
|
||||
|
||||
|
||||
@@ -11,7 +11,7 @@ helpviewer_keywords:
|
||||
ms.assetid: a4808397-c6d5-406a-83e0-0091f0c15ae4
|
||||
---
|
||||
# How to: Call a Page Function
|
||||
This example shows how to call a page function from a [!INCLUDE[TLA#tla_xaml](../../../includes/tlasharptla-xaml-md.md)] page.
|
||||
This example shows how to call a page function from a Extensible Application Markup Language (XAML) page.
|
||||
|
||||
## Example
|
||||
You can navigate to a page function using a uniform resource identifier (URI), just as you can when you navigate to a page. This is shown in the following example.
|
||||
|
||||
+2
-2
@@ -18,9 +18,9 @@ ms.assetid: c6e8c2cb-9ba2-4e75-a0d5-180ec9639433
|
||||
|
||||
# How to: Configure IIS 5.0 and IIS 6.0 to Deploy WPF Applications
|
||||
|
||||
You can deploy a [!INCLUDE[TLA#tla_winclient](../../../includes/tlasharptla-winclient-md.md)] application from most Web servers, as long as they are configured with the appropriate Multipurpose Internet Mail Extensions (MIME) types. By default, Microsoft Internet Information Services (IIS) 7.0 is configured with these MIME types, but Microsoft Internet Information Services (IIS) 5.0 and Microsoft Internet Information Services (IIS) 6.0 are not.
|
||||
You can deploy a Windows Presentation Foundation (WPF) application from most Web servers, as long as they are configured with the appropriate Multipurpose Internet Mail Extensions (MIME) types. By default, Microsoft Internet Information Services (IIS) 7.0 is configured with these MIME types, but Microsoft Internet Information Services (IIS) 5.0 and Microsoft Internet Information Services (IIS) 6.0 are not.
|
||||
|
||||
This topic describes how to configure Microsoft Internet Information Services (IIS) 5.0 and Microsoft Internet Information Services (IIS) 6.0 to deploy [!INCLUDE[TLA2#tla_winclient](../../../includes/tla2sharptla-winclient-md.md)] applications.
|
||||
This topic describes how to configure Microsoft Internet Information Services (IIS) 5.0 and Microsoft Internet Information Services (IIS) 6.0 to deploy WPF applications.
|
||||
|
||||
> [!NOTE]
|
||||
> You can check the *UserAgent* string in the registry to determine whether a system has .NET Framework installed. For details and a script that examines the *UserAgent* string to determine whether .NET Framework is installed on a system, see [Detect Whether the .NET Framework 3.0 Is Installed](how-to-detect-whether-the-net-framework-3-0-is-installed.md).
|
||||
|
||||
@@ -34,7 +34,7 @@ Windows Presentation Foundation (WPF) is a presentation framework that can be us
|
||||
|
||||
- Retrieving and processing command-line parameters.
|
||||
|
||||
- Sharing application-scope properties and [!INCLUDE[TLA2#tla_ui](../../../includes/tla2sharptla-ui-md.md)] resources.
|
||||
- Sharing application-scope properties and UI resources.
|
||||
|
||||
- Detecting and processing unhandled exceptions.
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ 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.
|
||||
Applications that host Windows Presentation Foundation (WPF) content via PresentationHost.exe implement this interface to provide a point of integration between the host and PresentationHost.exe.
|
||||
|
||||
## Remarks
|
||||
|
||||
|
||||
@@ -8,7 +8,7 @@ helpviewer_keywords:
|
||||
ms.assetid: f804648e-558c-4f60-8e48-d11f4a23c436
|
||||
---
|
||||
# Navigation How-to Topics
|
||||
The following topics show how to use [!INCLUDE[TLA#tla_winclient](../../../includes/tlasharptla-winclient-md.md)] navigation.
|
||||
The following topics show how to use Windows Presentation Foundation (WPF) navigation.
|
||||
|
||||
## In This Section
|
||||
[Call a Page Function](how-to-call-a-page-function.md)
|
||||
|
||||
@@ -31,7 +31,7 @@ ms.assetid: 86ad2143-606a-4e34-bf7e-51a2594248b8
|
||||
|
||||
Windows Presentation Foundation (WPF) supports browser-style navigation that can be used in two types of applications: standalone applications and XAML browser applications (XBAPs). To package content for navigation, WPF provides the <xref:System.Windows.Controls.Page> class. You can navigate from one <xref:System.Windows.Controls.Page> to another declaratively, by using a <xref:System.Windows.Documents.Hyperlink>, or programmatically, by using the <xref:System.Windows.Navigation.NavigationService>. WPF uses the journal to remember pages that have been navigated from and to navigate back to them.
|
||||
|
||||
<xref:System.Windows.Controls.Page>, <xref:System.Windows.Documents.Hyperlink>, <xref:System.Windows.Navigation.NavigationService>, and the journal form the core of the navigation support offered by WPF. This overview explores these features in detail before covering advanced navigation support that includes navigation to loose [!INCLUDE[TLA#tla_xaml](../../../includes/tlasharptla-xaml-md.md)] files, HTML files, and objects.
|
||||
<xref:System.Windows.Controls.Page>, <xref:System.Windows.Documents.Hyperlink>, <xref:System.Windows.Navigation.NavigationService>, and the journal form the core of the navigation support offered by WPF. This overview explores these features in detail before covering advanced navigation support that includes navigation to loose Extensible Application Markup Language (XAML) files, HTML files, and objects.
|
||||
|
||||
> [!NOTE]
|
||||
> In this topic, the term "browser" refers only to browsers that can host WPF applications, which currently includes Microsoft Internet Explorer and Firefox. Where specific WPF features are supported only by a particular browser, the browser version is referred to.
|
||||
@@ -75,13 +75,13 @@ This section explains and demonstrates the following aspects of navigation:
|
||||
|
||||
### Implementing a Page
|
||||
|
||||
In WPF, you can navigate to several content types that include .NET Framework objects, custom objects, enumeration values, user controls, [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] files, and HTML files. However, you'll find that the most common and convenient way to package content is by using <xref:System.Windows.Controls.Page>. Furthermore, <xref:System.Windows.Controls.Page> implements navigation-specific features to enhance their appearance and simplify development.
|
||||
In WPF, you can navigate to several content types that include .NET Framework objects, custom objects, enumeration values, user controls, XAML files, and HTML files. However, you'll find that the most common and convenient way to package content is by using <xref:System.Windows.Controls.Page>. Furthermore, <xref:System.Windows.Controls.Page> implements navigation-specific features to enhance their appearance and simplify development.
|
||||
|
||||
Using <xref:System.Windows.Controls.Page>, you can declaratively implement a navigable page of [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] content by using markup like the following.
|
||||
Using <xref:System.Windows.Controls.Page>, you can declaratively implement a navigable page of XAML content by using markup like the following.
|
||||
|
||||
[!code-xaml[NavigationOverviewSnippets#Page1XAML](~/samples/snippets/csharp/VS_Snippets_Wpf/NavigationOverviewSnippets/CSharp/Page1.xaml#page1xaml)]
|
||||
|
||||
A <xref:System.Windows.Controls.Page> that is implemented in [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] markup has `Page` as its root element and requires the WPF XML namespace declaration. The `Page` element contains the content that you want to navigate to and display. You add content by setting the `Page.Content` property element, as shown in the following markup.
|
||||
A <xref:System.Windows.Controls.Page> that is implemented in XAML markup has `Page` as its root element and requires the WPF XML namespace declaration. The `Page` element contains the content that you want to navigate to and display. You add content by setting the `Page.Content` property element, as shown in the following markup.
|
||||
|
||||
[!code-xaml[NavigationOverviewSnippets#Page2XAML](~/samples/snippets/csharp/VS_Snippets_Wpf/NavigationOverviewSnippets/CSharp/Page2.xaml#page2xaml)]
|
||||
|
||||
@@ -102,7 +102,7 @@ A markup-only <xref:System.Windows.Controls.Page> is useful for displaying conte
|
||||
|
||||
To allow a markup file and code-behind file to work together, the following configuration is required:
|
||||
|
||||
- In markup, the `Page` element must include the `x:Class` attribute. When the application is built, the existence of `x:Class` in the markup file causes Microsoft build engine (MSBuild) to create a `partial` class that derives from <xref:System.Windows.Controls.Page> and has the name that is specified by the `x:Class` attribute. This requires the addition of an XML namespace declaration for the [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] schema ( `xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"` ). The generated `partial` class implements `InitializeComponent`, which is called to register the events and set the properties that are implemented in markup.
|
||||
- In markup, the `Page` element must include the `x:Class` attribute. When the application is built, the existence of `x:Class` in the markup file causes Microsoft build engine (MSBuild) to create a `partial` class that derives from <xref:System.Windows.Controls.Page> and has the name that is specified by the `x:Class` attribute. This requires the addition of an XML namespace declaration for the XAML schema ( `xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"` ). The generated `partial` class implements `InitializeComponent`, which is called to register the events and set the properties that are implemented in markup.
|
||||
|
||||
- In code-behind, the class must be a `partial` class with the same name that is specified by the `x:Class` attribute in markup, and it must derive from <xref:System.Windows.Controls.Page>. This allows the code-behind file to be associated with the `partial` class that is generated for the markup file when the application is built (see [Building a WPF Application](building-a-wpf-application-wpf.md)).
|
||||
|
||||
@@ -214,9 +214,9 @@ The following shows an example of a `Hyperlink` that is configured to navigate t
|
||||
> This section describes the default fragment navigation implementation in WPF. WPF also allows you to implement your own fragment navigation scheme which, in part, requires handling the <xref:System.Windows.Navigation.NavigationService.FragmentNavigation?displayProperty=nameWithType> event.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> You can navigate to fragments in loose [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] pages (markup-only [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] files with `Page` as the root element) only if the pages can be browsed via HTTP.
|
||||
> You can navigate to fragments in loose XAML pages (markup-only XAML files with `Page` as the root element) only if the pages can be browsed via HTTP.
|
||||
>
|
||||
> However, a loose [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] page can navigate to its own fragments.
|
||||
> However, a loose XAML page can navigate to its own fragments.
|
||||
|
||||
<a name="NavigationService"></a>
|
||||
|
||||
@@ -367,7 +367,7 @@ Conceptually, the journal operates the same way that the **Back** and **Forward*
|
||||
|
||||
|
||||
|
||||
For XBAPs that are hosted by Internet Explorer, WPF integrates the journal into the navigation [!INCLUDE[TLA2#tla_ui](../../../includes/tla2sharptla-ui-md.md)] of Internet Explorer. This allows users to navigate pages in an XBAP by using the **Back**, **Forward**, and **Recent Pages** buttons in Internet Explorer.
|
||||
For XBAPs that are hosted by Internet Explorer, WPF integrates the journal into the navigation UI of Internet Explorer. This allows users to navigate pages in an XBAP by using the **Back**, **Forward**, and **Recent Pages** buttons in Internet Explorer.
|
||||
|
||||
> [!IMPORTANT]
|
||||
> In Internet Explorer, when a user navigates away from and back to an XBAP, only the journal entries for pages that were not kept alive are retained in the journal. For discussion on keeping pages alive, see [Page Lifetime and the Journal](#PageLifetime) later in this topic.
|
||||
@@ -537,7 +537,7 @@ The following are some of the ways that cookies are supported in WPF:
|
||||
|
||||
- XBAPs and HTML pages from the same domain can create and share cookies.
|
||||
|
||||
- Cookies are dispatched when XBAPs and loose [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] pages make Web requests.
|
||||
- Cookies are dispatched when XBAPs and loose XAML pages make Web requests.
|
||||
|
||||
- Both top-level XBAPs and XBAPs hosted in IFRAMES can access cookies.
|
||||
|
||||
@@ -608,7 +608,7 @@ As you can see, <xref:System.Windows.Navigation.NavigationWindow> displays Inter
|
||||
|
||||
If your pages provide their own journal navigation support and UI, you can hide the **Back** and **Forward** buttons displayed by <xref:System.Windows.Navigation.NavigationWindow> by setting the value of the <xref:System.Windows.Navigation.NavigationWindow.ShowsNavigationUI%2A> property to `false`.
|
||||
|
||||
Alternatively, you can use customization support in WPF to replace the [!INCLUDE[TLA2#tla_ui](../../../includes/tla2sharptla-ui-md.md)] of the <xref:System.Windows.Navigation.NavigationWindow> itself.
|
||||
Alternatively, you can use customization support in WPF to replace the UI of the <xref:System.Windows.Navigation.NavigationWindow> itself.
|
||||
|
||||
<a name="Frame_in_Standalone_Applications"></a>
|
||||
|
||||
@@ -642,12 +642,12 @@ The following figure illustrates the effect of navigating within a <xref:System.
|
||||
|
||||
|
||||
|
||||
Notice that the journal entries are shown by the navigation [!INCLUDE[TLA2#tla_ui](../../../includes/tla2sharptla-ui-md.md)] in the <xref:System.Windows.Controls.Frame>, rather than by Internet Explorer.
|
||||
Notice that the journal entries are shown by the navigation UI in the <xref:System.Windows.Controls.Frame>, rather than by Internet Explorer.
|
||||
|
||||
> [!NOTE]
|
||||
> If a <xref:System.Windows.Controls.Frame> is part of content that is hosted in a <xref:System.Windows.Window>, <xref:System.Windows.Controls.Frame> uses its own journal and, consequently, displays its own navigation [!INCLUDE[TLA2#tla_ui](../../../includes/tla2sharptla-ui-md.md)].
|
||||
> If a <xref:System.Windows.Controls.Frame> is part of content that is hosted in a <xref:System.Windows.Window>, <xref:System.Windows.Controls.Frame> uses its own journal and, consequently, displays its own navigation UI.
|
||||
|
||||
If your user experience requires a <xref:System.Windows.Controls.Frame> to provide its own journal without showing the navigation [!INCLUDE[TLA2#tla_ui](../../../includes/tla2sharptla-ui-md.md)], you can hide the navigation [!INCLUDE[TLA2#tla_ui](../../../includes/tla2sharptla-ui-md.md)] by setting the <xref:System.Windows.Controls.Frame.NavigationUIVisibility%2A> to <xref:System.Windows.Visibility.Hidden>. This is shown in the following markup.
|
||||
If your user experience requires a <xref:System.Windows.Controls.Frame> to provide its own journal without showing the navigation UI, you can hide the navigation UI by setting the <xref:System.Windows.Controls.Frame.NavigationUIVisibility%2A> to <xref:System.Windows.Visibility.Hidden>. This is shown in the following markup.
|
||||
|
||||
[!code-xaml[NavigationOverviewSnippets#FrameHostPageHidesUIXAML1](~/samples/snippets/csharp/VS_Snippets_Wpf/NavigationOverviewSnippets/CSharp/FrameHostPageOwnHiddenJournal.xaml#framehostpagehidesuixaml1)]
|
||||
[!code-xaml[NavigationOverviewSnippets#FrameHostPageHidesUIXAML2](~/samples/snippets/csharp/VS_Snippets_Wpf/NavigationOverviewSnippets/CSharp/FrameHostPageOwnHiddenJournal.xaml#framehostpagehidesuixaml2)]
|
||||
@@ -667,7 +667,7 @@ Besides using <xref:System.Windows.Navigation.NavigationService> and a journal,
|
||||
|
||||
|
||||
|
||||
This allows you to program navigation support directly against them. You may consider this if you need to provide a custom navigation [!INCLUDE[TLA2#tla_ui](../../../includes/tla2sharptla-ui-md.md)] for a <xref:System.Windows.Controls.Frame> that is hosted in a <xref:System.Windows.Window>. Furthermore, both types implement additional, navigation-related members, including `BackStack` (<xref:System.Windows.Navigation.NavigationWindow.BackStack%2A?displayProperty=nameWithType>, <xref:System.Windows.Controls.Frame.BackStack%2A?displayProperty=nameWithType>) and `ForwardStack` (<xref:System.Windows.Navigation.NavigationWindow.ForwardStack%2A?displayProperty=nameWithType>, <xref:System.Windows.Controls.Frame.ForwardStack%2A?displayProperty=nameWithType>), which allow you to enumerate the journal entries in the back stack and forward stack, respectively.
|
||||
This allows you to program navigation support directly against them. You may consider this if you need to provide a custom navigation UI for a <xref:System.Windows.Controls.Frame> that is hosted in a <xref:System.Windows.Window>. Furthermore, both types implement additional, navigation-related members, including `BackStack` (<xref:System.Windows.Navigation.NavigationWindow.BackStack%2A?displayProperty=nameWithType>, <xref:System.Windows.Controls.Frame.BackStack%2A?displayProperty=nameWithType>) and `ForwardStack` (<xref:System.Windows.Navigation.NavigationWindow.ForwardStack%2A?displayProperty=nameWithType>, <xref:System.Windows.Controls.Frame.ForwardStack%2A?displayProperty=nameWithType>), which allow you to enumerate the journal entries in the back stack and forward stack, respectively.
|
||||
|
||||
As mentioned earlier, more than one journal can exist within an application. The following figure provides an example of when this can happen.
|
||||
|
||||
@@ -679,21 +679,21 @@ As mentioned earlier, more than one journal can exist within an application. The
|
||||
|
||||
Throughout this topic, <xref:System.Windows.Controls.Page> and pack XBAPs have been used to demonstrate the various navigation capabilities of WPF. However, a <xref:System.Windows.Controls.Page> that is compiled into an application is not the only type of content that can be navigated to, and pack XBAPs aren't the only way to identify content.
|
||||
|
||||
As this section demonstrates, you can also navigate to loose [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] files, HTML files, and objects.
|
||||
As this section demonstrates, you can also navigate to loose XAML files, HTML files, and objects.
|
||||
|
||||
<a name="Navigating_to_Loose_XAML_Files"></a>
|
||||
|
||||
### Navigating to Loose XAML Files
|
||||
|
||||
A loose [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] file is a file with the following characteristics:
|
||||
A loose XAML file is a file with the following characteristics:
|
||||
|
||||
- Contains only [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] (that is, no code).
|
||||
- Contains only XAML (that is, no code).
|
||||
|
||||
- Has an appropriate namespace declaration.
|
||||
|
||||
- Has the .xaml file name extension.
|
||||
|
||||
For example, consider the following content that is stored as a loose [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] file, Person.xaml.
|
||||
For example, consider the following content that is stored as a loose XAML file, Person.xaml.
|
||||
|
||||
[!code-xaml[NavigationOverviewSnippets#LooseXAML](~/samples/snippets/csharp/VS_Snippets_Wpf/NavigationOverviewSnippets/CSharp/Person.xaml#loosexaml)]
|
||||
|
||||
@@ -701,7 +701,7 @@ When you double-click the file, the browser opens and navigates to and displays
|
||||
|
||||
|
||||
|
||||
You can display a loose [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] file from the following:
|
||||
You can display a loose XAML file from the following:
|
||||
|
||||
- A Web site on the local machine, the intranet, or the Internet.
|
||||
|
||||
@@ -709,18 +709,18 @@ You can display a loose [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-
|
||||
|
||||
- The local disk.
|
||||
|
||||
A loose [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] file can be added to the browser's favorites, or be the browser's home page.
|
||||
A loose XAML file can be added to the browser's favorites, or be the browser's home page.
|
||||
|
||||
> [!NOTE]
|
||||
> For more information about publishing and launching loose [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] pages, see [Deploying a WPF Application](deploying-a-wpf-application-wpf.md).
|
||||
> For more information about publishing and launching loose XAML pages, see [Deploying a WPF Application](deploying-a-wpf-application-wpf.md).
|
||||
|
||||
One limitation with respect to loose [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] is that you can only host content that is safe to run in partial trust. For example, `Window` cannot be the root element of a loose [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] file. For more information, see [WPF Partial Trust Security](../wpf-partial-trust-security.md).
|
||||
One limitation with respect to loose XAML is that you can only host content that is safe to run in partial trust. For example, `Window` cannot be the root element of a loose XAML file. For more information, see [WPF Partial Trust Security](../wpf-partial-trust-security.md).
|
||||
|
||||
<a name="Navigating_to_HTML_Files_Using_Frame"></a>
|
||||
|
||||
### Navigating to HTML Files by Using Frame
|
||||
|
||||
As you might expect, you can also navigate to HTML. You simply need to provide a URI that uses the http scheme. For example, the following [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] shows a <xref:System.Windows.Controls.Frame> that navigates to an HTML page.
|
||||
As you might expect, you can also navigate to HTML. You simply need to provide a URI that uses the http scheme. For example, the following XAML shows a <xref:System.Windows.Controls.Frame> that navigates to an HTML page.
|
||||
|
||||
[!code-xaml[NavigationOverviewSnippets#FrameHtmlNavMARKUP](~/samples/snippets/csharp/VS_Snippets_Wpf/NavigationOverviewSnippets/CSharp/FrameHTMLNavPage.xaml#framehtmlnavmarkup)]
|
||||
|
||||
|
||||
+4
-4
@@ -38,7 +38,7 @@ ms.assetid: 5d5ee837-629a-4933-869a-186dc22ac43d
|
||||
|
||||
These pages are arranged in a *navigation topology* whose structure is determined by how you can navigate between the pages. This particular navigation topology is suitable in simple scenarios, although navigation can require more complex topologies, some of which can only be defined when an application is running.
|
||||
|
||||
This topic covers three common navigation topologies: *fixed linear*, *fixed hierarchical*, and *dynamically generated*. Each navigation topology is demonstrated with a sample that has a [!INCLUDE[TLA2#tla_ui](../../../includes/tla2sharptla-ui-md.md)] like the one that is shown in the following figure:
|
||||
This topic covers three common navigation topologies: *fixed linear*, *fixed hierarchical*, and *dynamically generated*. Each navigation topology is demonstrated with a sample that has a UI like the one that is shown in the following figure:
|
||||
|
||||
|
||||
|
||||
@@ -60,7 +60,7 @@ ms.assetid: 5d5ee837-629a-4933-869a-186dc22ac43d
|
||||
|
||||
The typical behaviors for navigating over a fixed linear topology include the following:
|
||||
|
||||
- Navigating from the calling page to a launcher page that initializes the wizard and navigates to the first wizard page. A launcher page (a [!INCLUDE[TLA2#tla_ui](../../../includes/tla2sharptla-ui-md.md)]-less <xref:System.Windows.Navigation.PageFunction%601>) is not required, since a calling page can call the first wizard page directly. Using a launcher page, however, can simplify wizard initialization, particularly if initialization is complex.
|
||||
- Navigating from the calling page to a launcher page that initializes the wizard and navigates to the first wizard page. A launcher page (a UI-less <xref:System.Windows.Navigation.PageFunction%601>) is not required, since a calling page can call the first wizard page directly. Using a launcher page, however, can simplify wizard initialization, particularly if initialization is complex.
|
||||
|
||||
- Users can navigate between pages by using Back and Forward buttons (or hyperlinks).
|
||||
|
||||
@@ -88,7 +88,7 @@ ms.assetid: 5d5ee837-629a-4933-869a-186dc22ac43d
|
||||
|
||||
Even though the sequence in which pages in a fixed hierarchical structure are navigated is determined at run time, the user experience is the same as the user experience for a fixed linear topology:
|
||||
|
||||
- Navigating from the calling page to a launcher page that initializes the wizard and navigates to the first wizard page. A launcher page (a [!INCLUDE[TLA2#tla_ui](../../../includes/tla2sharptla-ui-md.md)]-less <xref:System.Windows.Navigation.PageFunction%601>) is not required, since a calling page can call the first wizard page directly. Using a launcher page, however, can simplify wizard initialization, particularly if initialization is complex.
|
||||
- Navigating from the calling page to a launcher page that initializes the wizard and navigates to the first wizard page. A launcher page (a UI-less <xref:System.Windows.Navigation.PageFunction%601>) is not required, since a calling page can call the first wizard page directly. Using a launcher page, however, can simplify wizard initialization, particularly if initialization is complex.
|
||||
|
||||
- Users can navigate between pages by using Back and Forward buttons (or hyperlinks).
|
||||
|
||||
@@ -118,7 +118,7 @@ ms.assetid: 5d5ee837-629a-4933-869a-186dc22ac43d
|
||||
|
||||
The navigation sequence is known as a dynamically generated topology. For the user, as with the other navigation topologies, the user experience is the same as it is for the previous topologies:
|
||||
|
||||
- Navigating from the calling page to a launcher page that initializes the wizard and navigates to the first wizard page. A launcher page (a [!INCLUDE[TLA2#tla_ui](../../../includes/tla2sharptla-ui-md.md)]-less <xref:System.Windows.Navigation.PageFunction%601>) is not required, since a calling page can call the first wizard page directly. Using a launcher page, however, can simplify wizard initialization, particularly if initialization is complex.
|
||||
- Navigating from the calling page to a launcher page that initializes the wizard and navigates to the first wizard page. A launcher page (a UI-less <xref:System.Windows.Navigation.PageFunction%601>) is not required, since a calling page can call the first wizard page directly. Using a launcher page, however, can simplify wizard initialization, particularly if initialization is complex.
|
||||
|
||||
- Users can navigate between pages by using Back and Forward buttons (or hyperlinks).
|
||||
|
||||
|
||||
@@ -15,7 +15,7 @@ ms.assetid: 43adb517-21a7-4df3-98e8-09e9cdf764c4
|
||||
|
||||
In Windows Presentation Foundation (WPF), uniform resource identifiers (URIs) are used to identify and load files in many ways, including the following:
|
||||
|
||||
- Specifying the [!INCLUDE[TLA#tla_ui](../../../includes/tlasharptla-ui-md.md)] to show when an application first starts.
|
||||
- Specifying the user interface (UI) to show when an application first starts.
|
||||
|
||||
- Loading images.
|
||||
|
||||
@@ -92,11 +92,11 @@ The pack URI for a resource file that is compiled into the local assembly uses t
|
||||
|
||||
- **Path**: The name of the resource file, including its path, relative to the local assembly project folder root.
|
||||
|
||||
The following example shows the pack URI for a [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] resource file that is located in the root of the local assembly's project folder.
|
||||
The following example shows the pack URI for a XAML resource file that is located in the root of the local assembly's project folder.
|
||||
|
||||
`pack://application:,,,/ResourceFile.xaml`
|
||||
|
||||
The following example shows the pack URI for a [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] resource file that is located in a subfolder of the local assembly's project folder.
|
||||
The following example shows the pack URI for a XAML resource file that is located in a subfolder of the local assembly's project folder.
|
||||
|
||||
`pack://application:,,,/Subfolder/ResourceFile.xaml`
|
||||
|
||||
@@ -122,15 +122,15 @@ The pack URI for a resource file that is compiled into a referenced assembly use
|
||||
|
||||
- **/Path**: the name of the resource file, including its path, relative to the root of the referenced assembly's project folder.
|
||||
|
||||
The following example shows the pack URI for a [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] resource file that is located in the root of the referenced assembly's project folder.
|
||||
The following example shows the pack URI for a XAML resource file that is located in the root of the referenced assembly's project folder.
|
||||
|
||||
`pack://application:,,,/ReferencedAssembly;component/ResourceFile.xaml`
|
||||
|
||||
The following example shows the pack URI for a [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] resource file that is located in a subfolder of the referenced assembly's project folder.
|
||||
The following example shows the pack URI for a XAML resource file that is located in a subfolder of the referenced assembly's project folder.
|
||||
|
||||
`pack://application:,,,/ReferencedAssembly;component/Subfolder/ResourceFile.xaml`
|
||||
|
||||
The following example shows the pack URI for a [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] resource file that is located in the root folder of a referenced, version-specific assembly's project folder.
|
||||
The following example shows the pack URI for a XAML resource file that is located in the root folder of a referenced, version-specific assembly's project folder.
|
||||
|
||||
`pack://application:,,,/ReferencedAssembly;v1.0.0.1;component/ResourceFile.xaml`
|
||||
|
||||
@@ -148,11 +148,11 @@ The pack URI for a content file uses the following authority and path:
|
||||
|
||||
- **Path**: The name of the content file, including its path relative to the file system location of the application's main executable assembly.
|
||||
|
||||
The following example shows the pack URI for a [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] content file, located in the same folder as the executable assembly.
|
||||
The following example shows the pack URI for a XAML content file, located in the same folder as the executable assembly.
|
||||
|
||||
`pack://application:,,,/ContentFile.xaml`
|
||||
|
||||
The following example shows the pack URI for a [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] content file, located in a subfolder that is relative to the application's executable assembly.
|
||||
The following example shows the pack URI for a XAML content file, located in a subfolder that is relative to the application's executable assembly.
|
||||
|
||||
`pack://application:,,,/Subfolder/ContentFile.xaml`
|
||||
|
||||
@@ -169,11 +169,11 @@ The pack URI for a site of origin file uses the following authority and path:
|
||||
|
||||
- **Path**: The name of the site of origin file, including its path relative to the location from which the executable assembly was launched.
|
||||
|
||||
The following example shows the pack URI for a [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] site of origin file, stored in the location from which the executable assembly is launched.
|
||||
The following example shows the pack URI for a XAML site of origin file, stored in the location from which the executable assembly is launched.
|
||||
|
||||
`pack://siteoforigin:,,,/SiteOfOriginFile.xaml`
|
||||
|
||||
The following example shows the pack URI for a [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] site of origin file, stored in subfolder that is relative to the location from which the application's executable assembly is launched.
|
||||
The following example shows the pack URI for a XAML site of origin file, stored in subfolder that is relative to the location from which the application's executable assembly is launched.
|
||||
|
||||
`pack://siteoforigin:,,,/Subfolder/SiteOfOriginFile.xaml`
|
||||
|
||||
@@ -183,7 +183,7 @@ The following example shows the pack URI for a [!INCLUDE[TLA2#tla_xaml](../../..
|
||||
|
||||
XAML files that are configured as MSBuild `Page` items are compiled into assemblies in the same way as resource files. Consequently, MSBuild `Page` items can be identified using pack URIs for resource files.
|
||||
|
||||
The types of [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] files that are commonly configured as MSBuild`Page` items have one of the following as their root element:
|
||||
The types of XAML files that are commonly configured as MSBuild`Page` items have one of the following as their root element:
|
||||
|
||||
- <xref:System.Windows.Window?displayProperty=nameWithType>
|
||||
|
||||
@@ -201,7 +201,7 @@ The types of [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)
|
||||
|
||||
## Absolute vs. Relative Pack URIs
|
||||
|
||||
A fully qualified pack URI includes the scheme, the authority, and the path, and it is considered an absolute pack URI. As a simplification for developers, [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] elements typically allow you to set appropriate attributes with a relative pack URI, which includes only the path.
|
||||
A fully qualified pack URI includes the scheme, the authority, and the path, and it is considered an absolute pack URI. As a simplification for developers, XAML elements typically allow you to set appropriate attributes with a relative pack URI, which includes only the path.
|
||||
|
||||
For example, consider the following absolute pack URI for a resource file in the local assembly.
|
||||
|
||||
@@ -398,7 +398,7 @@ The preceding sections have discussed how to construct pack URIs to identify res
|
||||
|
||||
#### Specifying the UI to Show When an Application Starts
|
||||
|
||||
<xref:System.Windows.Application.StartupUri%2A> specifies the first [!INCLUDE[TLA2#tla_ui](../../../includes/tla2sharptla-ui-md.md)] to show when a WPF application is launched. For standalone applications, the [!INCLUDE[TLA2#tla_ui](../../../includes/tla2sharptla-ui-md.md)] can be a window, as shown in the following example.
|
||||
<xref:System.Windows.Application.StartupUri%2A> specifies the first UI to show when a WPF application is launched. For standalone applications, the UI can be a window, as shown in the following example.
|
||||
|
||||
[!code-xaml[PackURIOverviewSnippets#StartupUriWindow](~/samples/snippets/csharp/VS_Snippets_Wpf/PackURIOverviewSnippets/CS/Copy of App.xaml#startupuriwindow)]
|
||||
|
||||
|
||||
+1
-1
@@ -69,7 +69,7 @@ Because the calling page can use the called page to collect and return data from
|
||||
[!code-csharp[StructuredNavigationSample#CalledPageFunctionCODEBEHIND2](~/samples/snippets/csharp/VS_Snippets_Wpf/StructuredNavigationSample/CSharp/CalledPageFunction.xaml.cs#calledpagefunctioncodebehind2)]
|
||||
[!code-vb[StructuredNavigationSample#CalledPageFunctionCODEBEHIND2](~/samples/snippets/visualbasic/VS_Snippets_Wpf/StructuredNavigationSample/VisualBasic/CalledPageFunction.xaml.vb#calledpagefunctioncodebehind2)]
|
||||
|
||||
The declaration of a <xref:System.Windows.Navigation.PageFunction%601> is similar to the declaration of a <xref:System.Windows.Controls.Page> with the addition of the type arguments. As you can see from the code example, the type arguments are specified in both [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] markup, using the `x:TypeArguments` attribute, and code-behind, using standard generic type argument syntax.
|
||||
The declaration of a <xref:System.Windows.Navigation.PageFunction%601> is similar to the declaration of a <xref:System.Windows.Controls.Page> with the addition of the type arguments. As you can see from the code example, the type arguments are specified in both XAML markup, using the `x:TypeArguments` attribute, and code-behind, using standard generic type argument syntax.
|
||||
|
||||
You don't have to use only .NET Framework classes as type arguments. A <xref:System.Windows.Navigation.PageFunction%601> could be called to gather domain-specific data that is abstracted as a custom type. The following code shows how to use a custom type as a type argument for a <xref:System.Windows.Navigation.PageFunction%601>.
|
||||
|
||||
|
||||
+1
-1
@@ -8,7 +8,7 @@ helpviewer_keywords:
|
||||
ms.assetid: 3090b408-94e4-446a-92ca-50f1fd36e5d8
|
||||
---
|
||||
# Window Management How-to Topics
|
||||
The following topics show how to manage [!INCLUDE[TLA#tla_winclient](../../../includes/tlasharptla-winclient-md.md)] windows.
|
||||
The following topics show how to manage Windows Presentation Foundation (WPF) windows.
|
||||
|
||||
## In This Section
|
||||
[Automatically Size a Window to Fit Its Content](how-to-automatically-size-a-window-to-fit-its-content.md)
|
||||
|
||||
+3
-3
@@ -20,7 +20,7 @@ helpviewer_keywords:
|
||||
ms.assetid: 7ad2943b-3961-41d3-8fc6-1582d43f5d99
|
||||
---
|
||||
# WPF Application Resource, Content, and Data Files
|
||||
Microsoft Windows applications often depend on files that contain non-executable data, such as [!INCLUDE[TLA#tla_xaml](../../../includes/tlasharptla-xaml-md.md)], images, video, and audio. Windows Presentation Foundation (WPF) offers special support for configuring, identifying, and using these types of data files, which are called application data files. This support revolves around a specific set of application data file types, including:
|
||||
Microsoft Windows applications often depend on files that contain non-executable data, such as Extensible Application Markup Language (XAML), images, video, and audio. Windows Presentation Foundation (WPF) offers special support for configuring, identifying, and using these types of data files, which are called application data files. This support revolves around a specific set of application data file types, including:
|
||||
|
||||
- **Resource Files**: Data files that are compiled into either an executable or library WPF assembly.
|
||||
|
||||
@@ -106,10 +106,10 @@ Microsoft Windows applications often depend on files that contain non-executable
|
||||
> [!NOTE]
|
||||
> In Visual Studio, you add a new <xref:System.Windows.Window>, <xref:System.Windows.Navigation.NavigationWindow>, <xref:System.Windows.Controls.Page>, <xref:System.Windows.Documents.FlowDocument>, or <xref:System.Windows.ResourceDictionary> to a project, the `Build Action` for the markup file will default to `Page`.
|
||||
|
||||
When a project with `Page` items is compiled, the [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] items are converted to binary format and compiled into the associated assembly. Consequently, these files can be used in the same way as typical resource files.
|
||||
When a project with `Page` items is compiled, the XAML items are converted to binary format and compiled into the associated assembly. Consequently, these files can be used in the same way as typical resource files.
|
||||
|
||||
> [!NOTE]
|
||||
> If a [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] file is configured as a `Resource` item, and does not have a code-behind file, the raw [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] is compiled into an assembly rather than a binary version of the raw [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)].
|
||||
> If a XAML file is configured as a `Resource` item, and does not have a code-behind file, the raw XAML is compiled into an assembly rather than a binary version of the raw XAML.
|
||||
|
||||
<a name="Content_Files"></a>
|
||||
## Content Files
|
||||
|
||||
@@ -10,7 +10,7 @@ ms.assetid: 3215bfa1-722c-4ac8-a7c5-bdd02d30afbd
|
||||
# WPF Host (PresentationHost.exe)
|
||||
Windows Presentation Foundation (WPF) Host (PresentationHost.exe) is the application that enables WPF applications to be hosted in compatible browsers (including Microsoft Internet Explorer 6 and later). By default, Windows Presentation Foundation (WPF) Host is registered as the shell and MIME handler for browser-hosted WPF content, which includes:
|
||||
|
||||
- Loose (uncompiled) [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] files (.xaml).
|
||||
- Loose (uncompiled) XAML files (.xaml).
|
||||
|
||||
- XAML browser application (XBAP) (.xbap).
|
||||
|
||||
|
||||
@@ -35,7 +35,7 @@ ms.assetid: 737d04ec-8861-46c3-8d44-fa11d3528d23
|
||||
Users interact with Windows Presentation Foundation (WPF) standalone applications through windows. The primary purpose of a window is to host content that visualizes data and enables users to interact with data. Standalone WPF applications provide their own windows by using the <xref:System.Windows.Window> class. This topic introduces <xref:System.Windows.Window> before covering the fundamentals of creating and managing windows in standalone applications.
|
||||
|
||||
> [!NOTE]
|
||||
> Browser-hosted WPF applications, including XAML browser applications (XBAPs) and loose [!INCLUDE[TLA#tla_xaml](../../../includes/tlasharptla-xaml-md.md)] pages, don't provide their own windows. Instead, they are hosted in windows provided by Windows Internet Explorer. See [WPF XAML Browser Applications Overview](wpf-xaml-browser-applications-overview.md).
|
||||
> Browser-hosted WPF applications, including XAML browser applications (XBAPs) and loose Extensible Application Markup Language (XAML) pages, don't provide their own windows. Instead, they are hosted in windows provided by Windows Internet Explorer. See [WPF XAML Browser Applications Overview](wpf-xaml-browser-applications-overview.md).
|
||||
|
||||
<a name="TheWindowClass"></a>
|
||||
## The Window Class
|
||||
@@ -73,18 +73,18 @@ Users interact with Windows Presentation Foundation (WPF) standalone application
|
||||
|
||||
<a name="DefiningAWindow"></a>
|
||||
## Implementing a Window
|
||||
The implementation of a typical window comprises both appearance and behavior, where *appearance* defines how a window looks to users and *behavior* defines the way a window functions as users interact with it. In WPF, you can implement the appearance and behavior of a window using either code or [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] markup.
|
||||
The implementation of a typical window comprises both appearance and behavior, where *appearance* defines how a window looks to users and *behavior* defines the way a window functions as users interact with it. In WPF, you can implement the appearance and behavior of a window using either code or XAML markup.
|
||||
|
||||
In general, however, the appearance of a window is implemented using [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] markup, and its behavior is implemented using code-behind, as shown in the following example.
|
||||
In general, however, the appearance of a window is implemented using XAML markup, and its behavior is implemented using code-behind, as shown in the following example.
|
||||
|
||||
[!code-xaml[WindowsOverviewSnippets#MarkupAndCodeBehindWindowMARKUP](~/samples/snippets/csharp/VS_Snippets_Wpf/WindowsOverviewSnippets/CSharp/MarkupAndCodeBehindWindow.xaml#markupandcodebehindwindowmarkup)]
|
||||
|
||||
[!code-csharp[WindowsOverviewSnippets#MarkupAndCodeBehindWindowCODEBEHIND](~/samples/snippets/csharp/VS_Snippets_Wpf/WindowsOverviewSnippets/CSharp/MarkupAndCodeBehindWindow.xaml.cs#markupandcodebehindwindowcodebehind)]
|
||||
[!code-vb[WindowsOverviewSnippets#MarkupAndCodeBehindWindowCODEBEHIND](~/samples/snippets/visualbasic/VS_Snippets_Wpf/WindowsOverviewSnippets/VisualBasic/MarkupAndCodeBehindWindow.xaml.vb#markupandcodebehindwindowcodebehind)]
|
||||
|
||||
To enable a [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] markup file and code-behind file to work together, the following are required:
|
||||
To enable a XAML markup file and code-behind file to work together, the following are required:
|
||||
|
||||
- In markup, the `Window` element must include the `x:Class` attribute. When the application is built, the existence of `x:Class` in the markup file causes Microsoft build engine (MSBuild) to create a `partial` class that derives from <xref:System.Windows.Window> and has the name that is specified by the `x:Class` attribute. This requires the addition of an XML namespace declaration for the [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] schema ( `xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"` ). The generated `partial` class implements the `InitializeComponent` method, which is called to register the events and set the properties that are implemented in markup.
|
||||
- In markup, the `Window` element must include the `x:Class` attribute. When the application is built, the existence of `x:Class` in the markup file causes Microsoft build engine (MSBuild) to create a `partial` class that derives from <xref:System.Windows.Window> and has the name that is specified by the `x:Class` attribute. This requires the addition of an XML namespace declaration for the XAML schema ( `xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"` ). The generated `partial` class implements the `InitializeComponent` method, which is called to register the events and set the properties that are implemented in markup.
|
||||
|
||||
- In code-behind, the class must be a `partial` class with the same name that is specified by the `x:Class` attribute in markup, and it must derive from <xref:System.Windows.Window>. This allows the code-behind file to be associated with the `partial` class that is generated for the markup file when the application is built (see [Building a WPF Application](building-a-wpf-application-wpf.md)).
|
||||
|
||||
@@ -93,7 +93,7 @@ Users interact with Windows Presentation Foundation (WPF) standalone application
|
||||
> [!NOTE]
|
||||
> When you add a new <xref:System.Windows.Window> to your project by using Visual Studio, the <xref:System.Windows.Window> is implemented using both markup and code-behind, and includes the necessary configuration to create the association between the markup and code-behind files as described here.
|
||||
|
||||
With this configuration in place, you can focus on defining the appearance of the window in [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] markup and implementing its behavior in code-behind. The following example shows a window with a button, implemented in [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] markup, and an event handler for the button's <xref:System.Windows.Controls.Primitives.ButtonBase.Click> event, implemented in code-behind.
|
||||
With this configuration in place, you can focus on defining the appearance of the window in XAML markup and implementing its behavior in code-behind. The following example shows a window with a button, implemented in XAML markup, and an event handler for the button's <xref:System.Windows.Controls.Primitives.ButtonBase.Click> event, implemented in code-behind.
|
||||
|
||||
[!code-xaml[WindowsOverviewWindowWithButtonSnippets#MarkupAndCodeBehindWindowMARKUP](~/samples/snippets/csharp/VS_Snippets_Wpf/WindowsOverviewWindowWithButtonSnippets/CSharp/MarkupAndCodeBehindWindow.xaml#markupandcodebehindwindowmarkup)]
|
||||
|
||||
@@ -102,7 +102,7 @@ Users interact with Windows Presentation Foundation (WPF) standalone application
|
||||
|
||||
<a name="ConfiguringWindowForMSBuild"></a>
|
||||
## Configuring a Window Definition for MSBuild
|
||||
How you implement your window determines how it is configured for MSBuild. For a window that is defined using both [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] markup and code-behind:
|
||||
How you implement your window determines how it is configured for MSBuild. For a window that is defined using both XAML markup and code-behind:
|
||||
|
||||
- XAML markup files are configured as MSBuild `Page` items.
|
||||
|
||||
@@ -408,7 +408,7 @@ Users interact with Windows Presentation Foundation (WPF) standalone application
|
||||
|
||||
- <xref:System.Windows.ResizeMode.CanResizeWithGrip>
|
||||
|
||||
As with <xref:System.Windows.Window.WindowStyle%2A>, the resize mode of a window is unlikely to change during its lifetime, which means that you'll most likely set it from [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] markup.
|
||||
As with <xref:System.Windows.Window.WindowStyle%2A>, the resize mode of a window is unlikely to change during its lifetime, which means that you'll most likely set it from XAML markup.
|
||||
|
||||
[!code-xaml[WindowsOverviewSnippets#ResizeModeWindowMARKUP1](~/samples/snippets/csharp/VS_Snippets_Wpf/WindowsOverviewSnippets/CSharp/ResizeModeWindow.xaml#resizemodewindowmarkup1)]
|
||||
|
||||
@@ -432,7 +432,7 @@ Users interact with Windows Presentation Foundation (WPF) standalone application
|
||||
|
||||
|
||||
|
||||
You can set <xref:System.Windows.Window.WindowStyle%2A> using either [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] markup or code; because it is unlikely to change during the lifetime of a window, you will most likely configure it using [!INCLUDE[TLA2#tla_xaml](../../../includes/tla2sharptla-xaml-md.md)] markup.
|
||||
You can set <xref:System.Windows.Window.WindowStyle%2A> using either XAML markup or code; because it is unlikely to change during the lifetime of a window, you will most likely configure it using XAML markup.
|
||||
|
||||
[!code-xaml[WindowsOverviewSnippets#WindowStyleWindowMARKUP1](~/samples/snippets/csharp/VS_Snippets_Wpf/WindowsOverviewSnippets/CSharp/WindowStyleWindow.xaml#windowstylewindowmarkup1)]
|
||||
|
||||
|
||||
Reference in New Issue
Block a user