Ok, I'm not sure when it happened but:
Normally when I debug in VB.NET and I encounter an error the Debuger stops the program and then goes to the error and hooks a line up to a box that explains the error message, like overflow, bad syntax, etc. About two days ago it stopped doing that. Now it just displays the error message with out anything to go on. I don't know what happened. But now I'm lost when I get a really vague error. I also can't mouse over a variable to see whats currently stored in it. I'm considering re-ghosting my system but I'm scared the settings may be stored in the project, any one happen to know how I broke it?
Update - I've narrowed the problem down, I think it has something to do with my custom control. When ever it's an error about the control it doesn't give help full information. Is there a way to pass on the error protection for a custom control that inherits from a real control?
Normally when I debug in VB.NET and I encounter an error the Debuger stops the program and then goes to the error and hooks a line up to a box that explains the error message, like overflow, bad syntax, etc. About two days ago it stopped doing that. Now it just displays the error message with out anything to go on. I don't know what happened. But now I'm lost when I get a really vague error. I also can't mouse over a variable to see whats currently stored in it. I'm considering re-ghosting my system but I'm scared the settings may be stored in the project, any one happen to know how I broke it?
Update - I've narrowed the problem down, I think it has something to do with my custom control. When ever it's an error about the control it doesn't give help full information. Is there a way to pass on the error protection for a custom control that inherits from a real control?
Last edited:
