[ This article is for Windows Phone 8 developers. If you’re developing for Windows 10, see the latest documentation. ]
Provides the basic functionality for propagating a synchronization context in various synchronization models.
Assembly: mscorlib (in mscorlib.dll)
Thetype exposes the following members.
|CreateCopy||When overridden in a derived class, creates a copy of the synchronization context.|
|Equals(Object)||Determines whether the specified Object is equal to the current Object. (Inherited from Object.)|
|Finalize||Allows an object to try to free resources and perform other cleanup operations before the Object is reclaimed by garbage collection. (Inherited from Object.)|
|GetHashCode||Serves as a hash function for a particular type. (Inherited from Object.)|
|GetType||Gets the Type of the current instance. (Inherited from Object.)|
|MemberwiseClone||Creates a shallow copy of the current Object. (Inherited from Object.)|
|OperationCompleted||When overridden in a derived class, responds to the notification that an operation has completed.|
|OperationStarted||When overridden in a derived class, responds to the notification that an operation has started.|
|Post||When overridden in a derived class, dispatches an asynchronous message to a synchronization context.|
|Send||When overridden in a derived class, dispatches a synchronous message to a synchronization context.|
|SetSynchronizationContext||Security Critical. Sets the current synchronization context.|
|SetThreadStaticContext||Security Critical. Sets the current context for thread static data.|
|ToString||Returns a string that represents the current object. (Inherited from Object.)|
The class is a base class that provides a free-threaded context with no synchronization.
The purpose of the synchronization model implemented by this class is to allow the internal asynchronous/synchronization operations of the common language runtime to behave properly with different synchronization models. This model also simplifies some of the requirements that managed applications have had to follow in order to work correctly under different synchronization environments.
Providers of synchronization models can extend this class and provide their own implementations for these methods.