CustomContentState Class

CustomContentState Class


CustomContentState enables the ability to navigate through different states of a single piece of source content without reloading the source content for each subsequent navigation.

Namespace:   System.Windows.Navigation
Assembly:  PresentationFramework (in PresentationFramework.dll)


public abstract class CustomContentState


Initializes a new instance of the CustomContentState class.


The name for the content that is stored in navigation history. The value of JournalEntryName is displayed from NavigationWindow, Frame, and Windows Internet Explorer 7 navigation UI.


Determines whether the specified object is equal to the current object.(Inherited from Object.)


Allows an object to try to free resources and perform other cleanup operations before it is reclaimed by garbage collection.(Inherited from Object.)


Serves as the default hash function. (Inherited from Object.)


Gets the Type of the current instance.(Inherited from Object.)


Creates a shallow copy of the current Object.(Inherited from Object.)

System_CAPS_pubmethodReplay(NavigationService, NavigationMode)

Called to reapply state to a piece of content when navigation occurs.


Returns a string that represents the current object.(Inherited from Object.)

By default, NavigationService does not store an instance of a content object in navigation history. Instead, NavigationService creates a new instance of the content object each time it is navigated to by using navigation history. This behavior is designed to avoid excessive memory consumption when large numbers and large pieces of content are being navigated to. Consequently, the state of the content is not remembered from one navigation to the next. However, WPF provides the ability to associate a piece of custom state with the navigation history entry for a piece of content.

Custom state that is associated with a navigation history entry must be a class that derives from CustomContentState. You associate a CustomContentState object with a navigation history entry by using one of the following techniques:


If you call the AddBackEntry method, you must handle the Navigating event or implement IProvideCustomContentState.

When the navigation history entry is navigated to, WPF checks to see if a custom CustomContentState object is associated with it. If so, it calls Replay to allow the custom CustomContentState object to apply the state it remembered from the previous navigation.

A custom CustomContentState class can override JournalEntryName to change the name that appears for the navigation history entry to which the CustomContentState object is associated. The value that JournalEntryName returns is visible from the navigation UI of the various navigators (Internet Explorer 7, NavigationWindow, Frame).

A class that derives from CustomContentState must be serializable, which means it must at least be augmented with SerializableAttribute, and optionally implement ISerializable.


When you store information in custom content state, you cannot store any references to the instance of the page for which you are remembering state if don’t want the content to be retained in memory. This prevents WPF from releasing the page instance, and defeats the purpose of the default navigation history behavior. If you must do this, consider using KeepAlive instead.

The following is an example of a CustomContentState implementation that overrides JournalEntryName.

.NET Framework
Available since 3.0

Any public static (Shared in Visual Basic) members of this type are thread safe. Any instance members are not guaranteed to be thread safe.

Return to top
© 2015 Microsoft