This API supports the .NET Framework infrastructure and is not intended to be used directly from your code.
Defines an environment for the objects that are resident inside it and for which a policy can be enforced.
Assembly: mscorlib (in mscorlib.dll)
Thetype exposes the following members.
|AllocateDataSlot||Infrastructure. Allocates an unnamed data slot.|
|AllocateNamedDataSlot||Infrastructure. Allocates a named data slot.|
|DoCallBack||Infrastructure. Executes code in another context.|
|Equals(Object)||Determines whether the specified object is equal to the current object. (Inherited from Object.)|
|Finalize||Infrastructure. Cleans up the backing objects for the nondefault contexts. (Overrides Object.Finalize().)|
|FreeNamedDataSlot||Infrastructure. Frees a named data slot on all the contexts.|
|Freeze||Infrastructure. Freezes the context, making it impossible to add or remove context properties from the current context.|
|GetData||Infrastructure. Retrieves the value from the specified slot on the current context.|
|GetHashCode||Serves as the default hash function. (Inherited from Object.)|
|GetNamedDataSlot||Infrastructure. Looks up a named data slot.|
|GetProperty||Infrastructure. Returns a specific context property, specified by name.|
|GetType||Gets the Type of the current instance. (Inherited from Object.)|
|MemberwiseClone||Creates a shallow copy of the current Object. (Inherited from Object.)|
|RegisterDynamicProperty||Infrastructure. Registers a dynamic property implementing the IDynamicProperty interface with the remoting service.|
|SetData||Infrastructure. Sets the data in the specified slot on the current context.|
|SetProperty||Infrastructure. Sets a specific context property by name.|
|ToString||Infrastructure. Returns a String class representation of the current context. (Overrides Object.ToString().)|
|UnregisterDynamicProperty||Infrastructure. Unregisters a dynamic property implementing the IDynamicProperty interface.|
A context is an ordered sequence of properties that define an environment for the objects resident inside it. Contexts get created during the activation process for objects that are configured to require certain automatic services, such as synchronization, transactions, just-in-time activation, security, and so on. Multiple objects can live inside a context.
Classes are marked with an instance of the ContextAttribute class, which provides the usage rules. Whenever a new object is instantiated, the .NET Framework finds a compatible or creates a new instance of the class for the object. Once an object is placed in a context, it stays in it for life. Classes that can be bound to a context are called context-bound classes. When accessed from another context, such classes are referenced directly by using a proxy. Any call from an object in one context to an object in another context will go through a context proxy and be affected by the policy that the combined context properties enforce.
A new object's context is generally chosen based on meta-data attributes on the class. This mechanism is extensible through custom attributes. These are known as static-context properties, which are compiled into the class meta-data. Dynamic-context properties (also known as configuration properties) can be applied and configured by administrators.
For more information on contexts, see [<topic://cpconboundariesprocessesapplicationdomainscontexts>].