J
Jeroen
I've posted a related question in this newsgroup before, see google
groups link:
http://groups.google.nl/group/micro...lidoperationexception&rnum=1#8d8051941dd4e2c4
We still experience the problem ever since we migrated from .NET 1.1
to 2.0. Some of the causes (amongst others bad code in destructors)
have been removed, drastically reducing the number of appearances of
of the dreaded 'InvalidOperationException' right after closing the
application.
However, our testers sometimes get an InvalidOperationException
without clear trace (it occurred in 'System.Windows.Forms', pffff)
when they have just closed the application.
My question then is, can you guys help me compile a list of possible
sources for the above kind of problem? To start of with the ones we
already caught:
- Starting new screens/dialogs/forms in destructors;
- Incorrectly disposing a WebBrowser control
- Meddling with the parent of a form
- ....?
Any suggestions would be appreciated
groups link:
http://groups.google.nl/group/micro...lidoperationexception&rnum=1#8d8051941dd4e2c4
We still experience the problem ever since we migrated from .NET 1.1
to 2.0. Some of the causes (amongst others bad code in destructors)
have been removed, drastically reducing the number of appearances of
of the dreaded 'InvalidOperationException' right after closing the
application.
However, our testers sometimes get an InvalidOperationException
without clear trace (it occurred in 'System.Windows.Forms', pffff)
when they have just closed the application.
My question then is, can you guys help me compile a list of possible
sources for the above kind of problem? To start of with the ones we
already caught:
- Starting new screens/dialogs/forms in destructors;
- Incorrectly disposing a WebBrowser control
- Meddling with the parent of a form
- ....?
Any suggestions would be appreciated