SafeHandle.DangerousRelease Method

The DangerousRelease method is the counterpart to DangerousAddRef. You should always match a call to the DangerousRelease method with a successful call to DangerousAddRef.

Caution

This method is intended for advanced users and must always be used carefully. To avoid leaking handle resources, always call this method inside a constrained execution region (CER), where a thread abort cannot interrupt processing. In the same way that unmatched DangerousAddRef calls can cause resource leaks, unmatched DangerousRelease calls can cause invalid handle states to become visible to other threads. Do not expose DangerousAddRef or DangerousRelease calls to untrusted code.

.NET Framework

.NET Framework Client Profile

Portable Class Library

.NET for Windows Store apps

• 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