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

// so suppress finalization.

GC.SuppressFinalize(this);

}

}

Notice that this Dispose() method has been updated to call GC.SuppressFinalize(), which

informs the CLR that it is no longer necessary to call the destructor when this object is garbage col-

lected, given that the unmanaged resources have already been freed via the Dispose() logic.

A Formalized Disposal Pattern

The current implementation of MyResourceWrapper does work fairly well; however, we are left with a

few minor drawbacks. First, the Finalize() and Dispose() methods each have to clean up the same

unmanaged resources. This could result in duplicate code, which can easily become a nightmare to

maintain. Ideally, you would define a private helper function that is called by either method.

Next, you would like to make sure that the Finalize() method does not attempt to dispose of

any managed objects, while the Dispose() method should do so. Finally, you would also like to

make sure that the object user can safely call Dispose() multiple times without error. Currently, our

Dispose() method has no such safeguards.

To address these design issues, Microsoft has defined a formal, prim-and-proper disposal pat-

tern that strikes a balance between robustness, maintainability, and performance. Here is the final

(and annotated) version of MyResourceWrapper, which makes use of this official pattern:

public class MyResourceWrapper : IDisposable

{