Carl,

The objects dispose themselves when they are memory collected.
Nothing tricky... its part of the design pattern.  For
OleDbConnection, an ancestor has

~Component()
{
   this.Dispose(false);
}

and Dispose is virtual.

You should call Dispose on IDisposables when you are finished because
it might be a while before the memory collector runs, but forgetting
will not cause "havoc".

-James

Here is a practical question. Suppose I have the following code:

   public partial class MyForm : Form
   {
       Font boldFont; //Used throughout MyForm

       public MyForm()
       {
           InitializeComponent();
           boldFont = new Font(myControl.Font, FontStyle.Bold);
       }

       //Other code using boldFont...
   }

Now, at some point boldFont is somehow automatically disposed of by the GC
(which I know very little about)?

I.e. I don't have to worry about whether boldFont is going to be disposed of
or not?

Or, should I implement a "better safe than sorry strategy" and let a
destructor explicitly dispose boldFont?

I do find this topic a bit confusing. It feels like .NET is telling me:
"With me you no longer have to worry about returning resources. I'll take
care of it for you ('Wow' feeling here!), unless I don't know how to... ('I
knew it was too good to be true' feeling here)".

Are there some web documents (or part of a book) that can explain this topic
in an easy to follow way?

Best Regards Carl Johansson