Differences between debugging 2 different projects??? Help

  • Thread starter Thread starter Peter van der Veen
  • Start date Start date
P

Peter van der Veen

Hi

I've something strange. There is a different when an error occurs in 2
differen project/solutions.

In one project when a get an error the debugger stops at the line
which causes the error and show the error window. This is normal.
(Title of the dialog = Microsoft Development Environment')

A second project doesn't do that. It shows another error dialog (the
one a normal user get) and shows not the line where the error occur.
(Title of the dialog = the name of the project/application)

Both the projects are in debug mode and not in the release mode

Any idea? Debugging is a crime now :(

Peter
 
Hi Peter,

Is it possible that before your breakpoint you have a try catch wherin you
have a messagebox. (This causes as well that your error is past by the
debugger when it is in that try catch).

Cor
 
No try and catch. It doesn't matter what kind of error and where in
the code you are. Always the different. Project 1 stops and list the
line with the error, project2 stops only with a (different) messeage
box.
I've tried it also on a different PC but it is the same.
 
* Peter van der Veen said:
I've something strange. There is a different when an error occurs in 2
differen project/solutions.

In one project when a get an error the debugger stops at the line
which causes the error and show the error window. This is normal.
(Title of the dialog = Microsoft Development Environment')

A second project doesn't do that. It shows another error dialog (the
one a normal user get) and shows not the line where the error occur.
(Title of the dialog = the name of the project/application)

Both the projects are in debug mode and not in the release mode
Click to expand...

Delete the project's "obj" and "bin" folders and try again.
 
Yep

I've also created a new solution tested it with one small form and the
debug was ok.
Then i added lets say form2 to the solution and load form2 from form1
and it gave the wrong debug on form2. Form1 gave the normal debug
message.

It looks like it has to do something with that form.

Is there some debug line info in the windows form generated code??
 
I think i fonud the cause of this behavior.

I deleted one for one the components on the form and tested.
When i deleted a specific one the bedug info got normal.
I added the form again and only deleted that component and it was
fine.

It's a third party componnent, so i can put this behavior there, but
how can a component change the way VB.NET displays the debug
information??

Peter
 
Back
Top