This print for content only-size & color not accurate 7" X 9-1/4" / casebound / malloy

■

Note

Structures and class types can both implement 

IDisposable

(unlike overriding 

Finalize()

, which is

reserved for class types), as the object user (not the garbage collector) invokes the 

Dispose()

method.

To illustrate the use of this interface, create a new C# Console Application named Simple-

Dispose. Here is an updated MyResourceWrapper class that now implements IDisposable, rather

than overriding System.Object.Finalize():

// Implementing IDisposable.

public class MyResourceWrapper : IDisposable

{

// The object user should call this method

// when they finish with the object.

public void Dispose()

{

// Clean up unmanaged resources...

// Dispose other contained disposable objects...

// Just for a test.

Console.WriteLine("***** In Dispose! *****");

}

}

Notice that a Dispose() method is not only responsible for releasing the type’s unmanaged

resources, but should also call Dispose() on any other contained disposable methods. Unlike

Finalize(), it is perfectly safe to communicate with other managed objects within a Dispose()

method. The reason is simple: the garbage collector has no clue about the IDisposable interface

and will never call Dispose(). Therefore, when the object user calls this method, the object is still

living a productive life on the managed heap and has access to all other heap-allocated objects.

The calling logic is straightforward:

C H A P T E R   8  

■

U N D E R S TA N D I N G   O B J E C T   L I F E T I M E

259

8849CH08.qxd  10/22/07  1:27 PM  Page 259

---

public class Program

{

static void Main()

{

Console.WriteLine("***** Fun with Dispose *****\n");