By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,524 Members | 1,330 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,524 IT Pros & Developers. It's quick & easy.

Differences between debugging 2 different projects??? Help

P: n/a
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
Nov 20 '05 #1
Share this Question
Share on Google+
8 Replies


P: n/a
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

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

Nov 20 '05 #2

P: n/a

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.

On Tue, 27 Jul 2004 12:35:04 +0200, "Cor Ligthert"
<no**********@planet.nl> wrote:
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

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


Nov 20 '05 #3

P: n/a
Peter

even when you start debugging with F11?

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.

On Tue, 27 Jul 2004 12:35:04 +0200, "Cor Ligthert"
<no**********@planet.nl> wrote:
Hi Peter,

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

Cor

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

Nov 20 '05 #4

P: n/a
* Peter van der Veen <pv*****@no.spam.ming.vanbrug.nl> scripsit:
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


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

--
M S Herfried K. Wagner
M V P <URL:http://dotnet.mvps.org/>
V B <URL:http://dotnet.mvps.org/dotnet/faqs/>
Nov 20 '05 #5

P: n/a

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??
On Tue, 27 Jul 2004 12:57:59 +0200, "Cor Ligthert"
<no**********@planet.nl> wrote:
Peter

even when you start debugging with F11?

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.

On Tue, 27 Jul 2004 12:35:04 +0200, "Cor Ligthert"
<no**********@planet.nl> wrote:
>Hi Peter,
>
>Is it possible that before your breakpoint you have a try catch wherinyou >have a messagebox. (This causes as well that your error is past by the
>debugger when it is in that try catch).
>
>Cor
>>
>> 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
>


Nov 20 '05 #6

P: n/a
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

On Tue, 27 Jul 2004 12:29:24 +0200, Peter van der Veen
<pv*****@no.spam.ming.vanbrug.nl> wrote:
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


Nov 20 '05 #7

P: n/a
Maybe because there is that try and catch in?

Cor

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

Nov 20 '05 #8

P: n/a
Don't know

Only the component on the form is enough.
On Tue, 27 Jul 2004 13:40:14 +0200, "Cor Ligthert"
<no**********@planet.nl> wrote:
Maybe because there is that try and catch in?

Cor

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


Nov 20 '05 #9

This discussion thread is closed

Replies have been disabled for this discussion.