CriticalHandle.Dispose Method

Source:

CriticalHandle.cs

Source:

CriticalHandle.cs

Source:

CriticalHandle.cs

public:
 virtual void Dispose();

public void Dispose ();

abstract member Dispose : unit -> unit
override this.Dispose : unit -> unit

Public Sub Dispose ()

Implements

Remarks

Calling the Close or Dispose method allows the resources to be freed. Unlike the SafeHandle class, this will always happen immediately since there is no reference count to indicate that other threads are using this handle. Therefore, you must employ a synchronization mechanism to ensure it is safe to call the Dispose method. Although most classes that use the CriticalHandle class do not need to provide a finalizer, this is sometimes necessary (for example, to flush out file buffers or to write some data back into memory). In this case, the class can provide a finalizer that is guaranteed to run before the CriticalHandle critical finalizer runs.

Call the Close or Dispose method when you are finished using the CriticalHandle object. The Close method leaves the CriticalHandle object in an unusable state.

Note Always call the Close or Dispose method before you release your last reference to the CriticalHandle object. Otherwise, the resources it is using will not be freed until the garbage collector calls the CriticalHandle object's Finalize method.

Source:

CriticalHandle.cs

Source:

CriticalHandle.cs

Source:

CriticalHandle.cs

protected:
 virtual void Dispose(bool disposing);

[System.Security.SecurityCritical]
protected virtual void Dispose (bool disposing);

protected virtual void Dispose (bool disposing);

[<System.Security.SecurityCritical>]
abstract member Dispose : bool -> unit
override this.Dispose : bool -> unit

abstract member Dispose : bool -> unit
override this.Dispose : bool -> unit

Protected Overridable Sub Dispose (disposing As Boolean)

Parameters

Attributes

SecurityCriticalAttribute

Remarks

You should never explicitly call the Dispose method with the disposing parameter set to false.