SafeHandle.Close Method

Calling the Close or Dispose method allows the resources to be freed. This might not happen immediately if other threads are using the same safe handle object, but will happen as soon as that is no longer the case. Although most classes that use the SafeHandle 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 SafeHandle critical finalizer runs.

Call the Close or Dispose method when you are finished using the SafeHandle object.

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

.NET Framework

.NET Framework Client Profile

• SecurityPermission 

  for permission to call unmanaged code. Security action: LinkDemand. Associated enumeration: SecurityPermissionFlag.UnmanagedCode

Windows 8, Windows Server 2012, Windows 7, Windows Vista SP2, Windows Server 2008 (Server Core Role not supported), Windows Server 2008 R2 (Server Core Role supported with SP1 or later; Itanium not supported)

The .NET Framework does not support all versions of every platform. For a list of the supported versions, see .NET Framework System Requirements.

Reference