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

// See if tonsOfObjects[9000] is still alive.

if (tonsOfObjects[9000] != null)

{

Console.WriteLine("Generation of tonsOfObjects[9000] is: {0}",

GC.GetGeneration(tonsOfObjects[9000]));

}

else

Console.WriteLine("tonsOfObjects[9000] is no longer alive.");

// Print out how many times a generation has been swept.

Console.WriteLine("\nGen 0 has been swept {0} times",

GC.CollectionCount(0));

Console.WriteLine("Gen 1 has been swept {0} times",

GC.CollectionCount(1));

Console.WriteLine("Gen 2 has been swept {0} times",

GC.CollectionCount(2));

Console.ReadLine();

}

Here, we have purposely created a very large array of object types (50,000 to be exact) for test-

ing purposes. As you can see from the output shown in Figure 8-6, even though this Main() method

only made one explicit request for a garbage collection (via the GC.Collect() method), the CLR per-

formed a number of them in the background.

Figure 8-6.

Interacting with the CLR garbage collector via System.GC

At this point in the chapter, I hope you feel more comfortable regarding the details of object

lifetime. The remainder of this chapter examines the garbage collection process a bit further by

addressing how you can build 

finalizable objects as well as disposable objects. Be very aware that the

following techniques will only be useful if you are building managed classes that maintain internal

unmanaged resources.