FxCop/Code Analysis will also tell you if you are using the Dispose pattern
incorrectly.
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Greg Keogh
Sent: Tuesday, April 13, 2010 4:56 PM
To: 'ozDotNet'
Subject: RE: Dispose surprise
If so, Dispos
If so, Dispose() should be calling GC.SuppressFinalize(this) to prevent
finalization.
D'OH! I forgot. I've got disposable class all over the place, and for some
stupid reason I forgot to SuppressFinalize in this class. The symptom is
obvious now that I look at it again (I should have started so
010 4:30 PM
To: ozDotNet
Subject: RE: Dispose surprise
Do you own these classes? If so, Dispose() should be calling
GC.SuppressFinalize(this) to prevent finalization. There's no point finalizing,
if you have been disposed.
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotn
Do you own these classes? If so, Dispose() should be calling
GC.SuppressFinalize(this) to prevent finalization. There's no point finalizing,
if you have been disposed.
From: ozdotnet-boun...@ozdotnet.com [mailto:ozdotnet-boun...@ozdotnet.com] On
Behalf Of Greg Keogh
Sent: Tuesday, April 13, 201
