|
-
Mar 16th, 2004, 10:53 AM
#1
Thread Starter
pathfinder
[:RESOLVED:]VBNet: Break on Error: Being DisAssed!
This has been bugging me lately.
When I first started working in VB.Net, an error message something like this:
An unhandled exception of type 'System.NullReferenceException' occurred in MHex01.exe
Additional information: Object reference not set to an instance of an object.
Would, when I selected the "Break" button, would bring me to the forms code that produced the error, with the offending line highlighted and arrowed.
Nowadays, any New Project, upon "Breaking", thows me at the Dissassembly code.
I've gone through the switches in the project setup, {not today, but several times in the past couple of weeks}, but nothing jumps out at me as to something I could activate/deactivate to get it back into the "Normal" Code Highlighting mode.
Although, I did just go back to my first project, added :
VB Code:
Dim A as Integer
MsgBox("A(0)")
into the form load event, and sure'nuff, it brought me back to the MsgBox Line.
Doing the Same in my newest VBNet Project, I am forced to look at the DisAss code.
Anybody have Any hints to what I need to do to stay out of the DisAss?
At least now, with that MsgBox, I 99% Know its a setting issue, and not a ReInstall issue. So, If I make a New Project, VBNet resorts to its current Defaults, but if I open a previous Project, it resets to that projects "settings", so the differences must be visible if I compare an older projects control files to the same of a newer project. hmmm...
Last edited by NotLKH; Mar 16th, 2004 at 10:59 AM.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|