Checking for Objects that implement IDisposable but aren't properly disposed

Question

Is there a way to automatically check existing C# source code for instances of objects that are not properly disposed of ie. using try / catch / finally or using statements? Or do I need to just manually look at the code?

score 3 · Accepted Answer · answered Apr 08 '10 at 19:45

3

Take a look at FxCop for VS2010 - I believe they restored the DisposeObjectsBeforeLeavingScope rule - which may do exactly what you want.

answered Apr 08 '10 at 19:45

LBushkin

129,300
32
216
265

I downloaded the Trial version of VS2010 Premium and it does indeed have this rule CA2000. Thanks. – etoisarobot Apr 23 '10 at 20:06

score 1 · Answer 2 · edited May 23 '17 at 10:27

1

Use FX Cop for a rule to check if IDisposable are placed in a proper Using block...
You can use reflector to go through the object with IDisposable
Ref.: Is there a list of common object that implement IDisposable for the using statement? for additional idea

HTH

edited May 23 '17 at 10:27

Community

1
1

answered Apr 08 '10 at 19:46

Sunny

6,286
2
25
27

score 0 · Answer 3 · answered Apr 08 '10 at 20:43

CodeRush has some support for spotting obvious variants of this. Another possible option is (perhaps via an optional compilation symbol) add a finalizer to your own IDisposable objects, and complain loudly if they get finalized without being disposed (set a bool flag in the Dispose). But note: having a finalizer changes the behaviour of the objects, so don't leave it in production code (or even your regular unit tests).

Checking for Objects that implement IDisposable but aren't properly disposed

3 Answers3