Updated: December 2009
Assembly: PresentationFramework (in PresentationFramework.dll)
XMLNS for XAML: http://schemas.microsoft.com/winfx/2006/xaml/presentation, http://schemas.microsoft.com/netfx/2007/xaml/presentation
encapsulates a page of content that can be navigated, and has the following key members:
Lifetime Management: KeepAlive.
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 has designer support in Microsoft Visual Studio.
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.
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:
The following example shows how a standard page is defined using only code:
The following example shows how a standard page is defined using a combination of markup and code-behind.
Windows 7, Windows Vista, Windows XP SP2, Windows Server 2008 R2, Windows Server 2008, Windows Server 2003
The .NET Framework and .NET Compact Framework do not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.