Page encapsulates a page of content that can be navigated, and has the following key members:

• Lifetime Management: KeepAlive.

• Navigation: NavigationService.

• Appearance: Background, Content, FontFamily, FontSize, Foreground, ShowsNavigationUI, Template, Title.

• Host Window Appearance: WindowHeight, WindowWidth, WindowTitle.

A page can be defined by using markup, markup and code-behind, or code. A page is the preferred way to package content for navigation, for the following reasons:

• It is easy to define, reuse, and manage.

• It can access and use the NavigationService that navigated to it.

• It can alter the title, width, height, and navigation UI of its host window (WindowTitle, WindowWidth, WindowHeight, ShowsNavigationUI).

• It has designer support in Microsoft Visual Studio.

A page can be hosted from Window, NavigationWindow, or Frame, or from a browser. To be hosted, a page can be:

• The direct child of a Window, NavigationWindow, or Frame element in XAML.

• Instantiated and set as the value of the Content property of Window, NavigationWindow, and Frame.

• Set as the uniform resource identifier (URI) source of the Source property of either NavigationWindow or Frame.

• Set as the StartupUri in a standalone application.

• Set as the StartupUri in an XBAP.

An application typically has two or more pages, which can be navigated between using the following mechanisms:

• Declaratively by using Hyperlink.

• Programmatically by using NavigationService.

• Visually by using the navigation UI of the host, including Windows Internet Explorer, NavigationWindow, and Frame.

For structured navigation using page functions (PageFunction<(Of <(T>)>)), see Structured Navigation Overview and Navigation Topologies Overview.

Dependency properties for this control might be set by the control’s default style. If a property is set by a default style, the property might change from its default value when the control appears in the application. The default style is determined by which desktop theme is used when the application is running. For more information, see Themes.

The following example shows how a standard page is defined using only markup:

<Page 
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    Title="Markup Page">
  <!-- Page Content Goes Here -->
</Page>

The following example shows how a standard page is defined using only code:

using System.Windows.Controls;

public class CodePage : Page
{
    public CodePage() {}
}

The following example shows how a standard page is defined using a combination of markup and code-behind.

<Page 
    xmlns="http://schemas.microsoft.com/winfx/2006/xaml/presentation"
    xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
    x:Class="MarkupAndCodeBehindPage"
    Title="Markup And Code-Behind Page">
  <!-- Page Content Goes Here -->
</Page>

using System.Windows.Controls;

public partial class MarkupAndCodeBehindPage : Page
{
    public MarkupAndCodeBehindPage()
    {
        InitializeComponent();
    }
}

Windows 7, Windows Vista, Windows XP SP2, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003

.NET Framework

Reference

Other Resources