Hello Marty,
Thanks for your post. As I understand, the problem you are facing is how to
figure out the problem which causes "object reference not set to an
instance of an object". Please correct me if there is any misunderstanding.
I now share the following information with you:
Generally speaking, this error is caused when you declare a class variable
and use it without instantiating it. Such problem is easy to be identified
from the call stack when the exception throws. As you know, we are able to
dump the call stack in try/catch. Without try/catch code, you need to get
the symbole file (.pdb file) of the application, attach VS .NET debugger to
the process of it, and then we can view the call stack. Another method is
to use a tool say, ADPlus, to create a dump file when a process crashes,
open the dump file in a debugger say, windbg, to check the probolem.
In the meantime, I believe the following MSDN article is very helpful for
debugging .NET application:
Production Debugging for .NET Framework Applications
http://msdn.microsoft.com/library/de...us/dnbda/html/
DBGch01.asp
Please feel free to let me know if you have any problems or concerns.
Regards,
HuangTM
Microsoft Online Partner Support
MCSE/MCSD
Get Secure! --
www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.