This documentation is archived and is not being maintained.

SafeHandle.DangerousRelease Method

Note: This method is new in the .NET Framework version 2.0.

Manually decrements the reference counter on a SafeHandle instance.

Namespace: System.Runtime.InteropServices
Assembly: mscorlib (in mscorlib.dll)

public:
void DangerousRelease ()
public void DangerousRelease ()
public function DangerousRelease ()

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 noteCaution

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.

The following code example demonstrates how to use the DangerousAddRef, DangerousGetHandle, and DangerousRelease with a custom class called the MySafeHandle class that implements the SafeHandle class.

No code example is currently available or this language may not be supported.

Windows 98, Windows 2000 SP4, Windows Millennium Edition, Windows Server 2003, Windows XP Media Center Edition, Windows XP Professional x64 Edition, Windows XP SP2, Windows XP Starter Edition

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

.NET Framework

Supported in: 2.0
Show: