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

// Compile-time error!

protected override void Finalize(){ }

}

Rather, when you wish to configure your custom C# class types to override the Finalize()

method, you make use of a (C++-like) destructor syntax to achieve the same effect. The reason for

this alternative form of overriding a virtual method is that when the C# compiler processes the

finalizer syntax, it will automatically add a good deal of required infrastructure within the implicitly

overridden Finalize() method (shown in just a moment).

C# finalizers look very similar to a constructor in that they are named identically to the class

they are defined within. In addition, finalizers are prefixed with a tilde symbol (~). Unlike a con-

structor, however, finalizers never take an access modifier (they are implicitly protected), never take

parameters and cannot be overloaded (only one finalizer per class).

Here is a custom finalizer for MyResourceWrapper that will issue a system beep when invoked.

Obviously this is only for instructional purposes. A real-world finalizer would do nothing more than

free any unmanaged resources and would 

not interact with other managed objects, even those ref-

erenced by the current object, as you cannot assume they are still alive at the point the garbage

collector invokes your Finalize() method: