This documentation is archived and is not being maintained.

SearchResultCollection.Dispose Method (Boolean)

Releases the unmanaged resources that are used by the SearchResultCollection object and optionally releases the managed resources.

Namespace:  System.DirectoryServices
Assembly:  System.DirectoryServices (in System.DirectoryServices.dll)

protected virtual void Dispose(
	bool disposing


Type: System.Boolean
true to release both managed and unmanaged resources; false to release only unmanaged resources.

This method is called by the public Dispose method and the Finalize method. Dispose invokes the protected Dispose method with the disposing parameter set to true. Finalize invokes Dispose with the disposing parameter set to false.

When the disposing parameter is true, this method releases all resources that are held by any managed objects that this SearchResultCollection references.

The garbage collector does not release memory for a SearchResultCollection object. Therefore, you must call the Dispose method explicitly to prevent a memory leak.

This method invokes the Dispose method of each object in the collection.

For more information about Dispose() and Finalize, see Cleaning Up Unmanaged Resources and Overriding the Finalize Method.

Notes to Inheritors

The Dispose() method can be called multiple times by other objects. When overriding the Dispose(Boolean) method be careful not to reference objects that have been previously disposed of in an earlier call to the Dispose() method. For more information about how to implement Dispose(), see Implementing a Dispose Method.

.NET Framework

Supported in: 4, 3.5, 3.0, 2.0, 1.1, 1.0

.NET Framework Client Profile

Supported in: 4, 3.5 SP1

Windows 7, Windows Vista SP1 or later, Windows XP SP3, Windows XP SP2 x64 Edition, Windows Server 2008 (Server Core not supported), Windows Server 2008 R2 (Server Core supported with SP1 or later), Windows Server 2003 SP2

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