ContextStack Class


The .NET API Reference documentation has a new home. Visit the .NET API Browser on to see the new experience.

Provides a stack object that can be used by a serializer to make information available to nested serializers.

Namespace:   System.ComponentModel.Design.Serialization
Assembly:  System (in System.dll)


[HostProtectionAttribute(SecurityAction.LinkDemand, SharedState = true)]
[PermissionSetAttribute(SecurityAction.LinkDemand, Name = "FullTrust")]
public sealed class ContextStack


Initializes a new instance of the ContextStack class.


Gets the current object on the stack.


Gets the object on the stack at the specified level.


Gets the first object on the stack that inherits from or implements the specified type.


Appends an object to the end of the stack, rather than pushing it onto the top of the stack.


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


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


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


Removes the current object off of the stack, returning its value.


Pushes, or places, the specified object onto the stack.


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

Some serializers require information about the context of an object to correctly persist their state. The ContextStack class enables a serializer to set data about the context of an object that is being serialized to a stack where another serializer can access it. The value of the Context property is provided by an IDesignerSerializationManager to share information of use to some serializers.

A context stack is useful because the process of serializing a design document can be deeply nested, and objects at each level of nesting may require context information to correctly persist the state of the object. A serializer can set a context object to the stack before invoking a nested serializer. Each object set to the stack should be removed by the serializer that set it after a call to a nested serializer returns.

Typically, the objects on the stack contain information about the context of the current object that is being serialized. A parent serializer adds context information to the stack about the next object to be serialized, calls an appropriate serializer and, when the serializer finishes executing on the object, removes the context information from the stack. It is up to the implementation of each serializer to determine what objects get pushed on this stack.

As an example, an object with a property named Enabled has a data type of Boolean. If a serializer writes this value to a data stream, it might need to include the context or type of property it is writing. The serializer does not have this information, however, because it is only instructed to write the Boolean value. To provide this information to the serializer, the parent serializer can push a PropertyDescriptor that points to the Enabled property on the context stack.

The following code example demonstrates using a ContextStack to push and then remove 10 values.

using System;
using System.ComponentModel;
using System.ComponentModel.Design;
using System.ComponentModel.Design.Serialization;
using System.Windows.Forms;

namespace ContextStackExample
    class ContextStackExample
        static void Main(string[] args)
            // Create a ContextStack.
            ContextStack stack = new ContextStack();

            // Push ten items on to the stack and output the value of each.
            for( int number = 0; number < 10; number ++ )
                Console.WriteLine( "Value pushed to stack: "+number.ToString() );
                stack.Push( number );

            // Pop each item off the stack.
            object item = null;
            while( (item = stack.Pop()) != null )
                Console.WriteLine( "Value popped from stack: "+item.ToString() );


for full access to system resources. Demand values: LinkDemand, InheritanceDemand. Associated state:

.NET Framework
Available since 1.1

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