Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Given this stack
But short of starting from scratch and producing a perfectly unit tested project, is there a strategy (or app/module) to eliminating the generic msg Object reference not set to an instance of an object. and throwing something more specific? Something akin to what ELMAH can do with exceptions?
thx
Looking at the exception stack trace and identifying the exact line where the exception is thrown is the best indication to pinpoint the problem. When you have identified the line of code on which this exception is thrown you will already have a strong indication of its origin. Narrowing it down to a simple project always help if you are not able to understand why it might occur. Given the stack you have shown there is close to ∞ possibilities of why this might be happening.
Don’t expect to get anything more specific than this exception and the line on which it occurs.