Debugging and output messages advice needed 1

[golcarlad]

Whilst I am debugging my prog I get the following errors:

A first chance exception of type 'System.ObjectDisposedException' occurred in System.Windows.Forms.dll

A first chance exception of type 'System.NullReferenceException' occurred in Foo.dll

They dont stop my code running - they just appear in the "Output" window of Visual Studio.

Whats going on? are they something I should be worried about , should I be trying to stop these type of messages occuring by more closely debugging my program and fixing the code?

 

[Mibble]

post some code, perhaps we can help.

 

[golcarlad]

I cant find where in the code the errors start as it just dumps them out to the output window - is there a way to set the degugger to halt even on the tiniest of errors?

 

[misterstick]

project -> properties -> build -> treat warnings as errors -> all.

don't know if this catches first chance exceptions, though.



mr s. <

 

[golcarlad]

thanks mate - not sure whether that means warnings on compile?? - but anyway.

Actually found what these strange errors were. The were objects that were hanging around after a form was destroyed/closed - the form had some unmanaged COM object references that were not properly released OnDispose event - so I still had some other treenodes hanging around that were creating a System.ObjectDisposedException. Anyway I think thats what happening - 90% sure anyway - still trying to get to grips with the lower level understanding of memory storage on the heap/stack etc (oh what joy!!).

 

[chiph]

Run FxCop (aka CodeAnalysis) against your solution. It's pretty good at identifying areas where you need to Dispose of a resource.

Chip H.


____________________________________________________________________
If you want to get the best response to a question, please read FAQ222-2244 first

 

[golcarlad]

I like that FxCop - it seems to work quite well - found quite a few silly errors in the first couple of minutes which I was quite impressed with.