Is it possible to drill down far enough to figure out what an exception message means?
I am guessing the CORE .NET source code is not available to me so I can figure out WHY I am getting an error message and how to work-around the problem?
Sometimes the exception messages I get only tell me the problem....they don't really point to a solution at all or give me any indication of what I could do differently. So I sit there just feeling lost and very frustrated.
I know that if I set a breakpoint in the Catch block and then start drilling down through the Locals Window variables...I can obtain SOME clues as to what is going on.
I am just wondering if there is something that can help me with debugging? I am faithfully using Exception Handling....and this actually DOES help me very much....but sometimes it does not seem to help me.
LOL....am I just too stupid to be a programmer? When I spend hours on a single line of code I start to wonder. I'm kidding....but the frustration is real.
If there is some big secret to debugging that you gurus know about....please share it with me.
If spending hours debugging just one or two lines of code is NORMAL in industry....please tell me this also.....so I can align my expectations a little better about how fast I should be putting out code.
Even if I had a few techniques to help shorten the amount of time I spend on a problem that would also be helpful.