Barrier.Dispose Method
Definition
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Releases resources used by the current instance of the Barrier class.
Overloads
| Dispose() |
Releases all resources used by the current instance of the Barrier class. |
| Dispose(Boolean) |
Releases the unmanaged resources used by the Barrier, and optionally releases the managed resources. |
Dispose()
- Source:
- Barrier.cs
- Source:
- Barrier.cs
- Source:
- Barrier.cs
Releases all resources used by the current instance of the Barrier class.
public:
virtual void Dispose();public void Dispose ();abstract member Dispose : unit -> unit
override this.Dispose : unit -> unitPublic Sub Dispose ()Implements
Exceptions
The method was invoked from within a post-phase action.
Remarks
Call Dispose when you are finished using the Barrier. The Dispose method leaves the Barrier in an unusable state. After calling Dispose, you must release all references to the Barrier so the garbage collector can reclaim the memory that the Barrier was occupying.
For more information, see Cleaning Up Unmanaged Resources and Implementing a Dispose Method.
Note
Always call Dispose before you release your last reference to the Barrier. Otherwise, the resources it is using will not be freed until the garbage collector calls the Barrier object's Finalize method.
See also
Applies to
Dispose(Boolean)
- Source:
- Barrier.cs
- Source:
- Barrier.cs
- Source:
- Barrier.cs
Releases the unmanaged resources used by the Barrier, and optionally releases the managed resources.
protected:
virtual void Dispose(bool disposing);protected virtual void Dispose (bool disposing);abstract member Dispose : bool -> unit
override this.Dispose : bool -> unitProtected Overridable Sub Dispose (disposing As Boolean)Parameters
- disposing
- Boolean
true to release both managed and unmanaged resources; false to release only unmanaged resources.
Remarks
Unlike most of the members of Barrier, Dispose is not thread-safe and may not be used concurrently with other members of this instance.
