Lost error in a namespace

[dnagroove]

Hello to all and thank you for your attention...

I've built a solution with several projects, each project is a namespace, except for the main project which has all of the aspx files. The problem is that there is one namespace that generates an error ('Object reference not set to an instance of an object') but the line returned is the line that initiates the class within the ASPX file, instead of the line inside the namespace - where the error actually is.

Is there a certain declaration property of the namesapce/class? How can I find the actual line inside the namespace?

Thanks again.

[rdove]

You could set a break point on the call and use f11 for step through the code line by line.

Or if you could put all your code in a try..catch block and use the throw keyword.

Try
    'Some code here
Catch
    Throw
End Try

[dnagroove]

Thanks for your reply... but I was hoping for a magical way to trace the exact error line across projects. F11 doesn't go into the code because the problem is within the namespace DLL after it has been compiled, and a Try..Catch block is way too tedious with this particular project (image/file manipulation).

MS newsgroups say little about it, other than that it'll be less of an issue in .NET 2... pfft.

Thanks again, though.

[rdove]

Thanks for your reply... but I was hoping for a magical way to trace the exact error line across projects. F11 doesn't go into the code because the problem is within the namespace DLL after it has been compiled, and a Try..Catch block is way too tedious with this particular project (image/file manipulation).

MS newsgroups say little about it, other than that it'll be less of an issue in .NET 2... pfft.

Thanks again, though.

If you compile your project for debug (not release) it will create a debugger file along with your dll. Then you can use f11 to step through.

[dnagroove]

Wow... now that you've mentioned it, it appears I was indeed working on Release mode... and the F11 does help very much now.

Thank you!