Unhandled Exception in Form Load in EXE but not in IDE

[Mark Lewis]

I have a weird error trapping problem. When running the IDE everything works
fine but not when running in an EXE I get the Unhandled Exception Error
message box intead of the one in my Try....Catch Block.

To see this create a simple application with two forms. Form 1 should have
one button. The code is follows. Run this in the IDE and observe the error
and then compare that behavior to what happens when you run the built EXE.

Has anyone seen this?

Thanks,

Mark

=============== =============== =============== ==

Public Class Form1

Private Sub Button1_Click(B yVal sender As System.Object, ByVal e As
System.EventArg s) Handles Button1.Click

Dim f As New Form2
Try

f.Show()

Catch ex As Exception

MessageBox.Show (ex.Message)
f.Dispose()

End Try
End Sub
End Class
Public Class Form2

Private Sub Form2_Load(ByVa l sender As System.Object, ByVal e As
System.EventArg s) Handles MyBase.Load

Throw New ApplicationExce ption("error thrown in form2 load")

End Sub

End Class

[Walter Wang [MSFT]]

Hi Mark,

Thank you for sharing your findings with the community.

Regards,
Walter Wang (wa****@online. microsoft.com, remove 'online.')
Microsoft Online Community Support

=============== =============== =============== =====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no rights.

[Mark Lewis]

Would you think this is a bug in the EXE or in the IDE. It would be best if
the two would work the same.

Mark

"Walter Wang [MSFT]" <wa****@online. microsoft.comwr ote in message
news:uF******** ******@TK2MSFTN GXA01.phx.gbl.. .

Hi Mark,

Thank you for sharing your findings with the community.

Regards,
Walter Wang (wa****@online. microsoft.com, remove 'online.')
Microsoft Online Community Support

=============== =============== =============== =====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no
rights.

[Yan-Hong Huang[MSFT]]

Hello Mark,

Walter is taking leave this week. Is it OK for us to work with you next
week for it if this is not urgent?

Based on my experience, if we can get a repro sample, we can definitely
forward that to our product team for further analysis. This may need some
more time. But please rest assured that we will do our best to work with
you.

Surely you can also talk to our development directly and report it. Please
use the following web link:
http://connect.microsoft.com/site/si...spx?SiteID=210

If you feel there is any we can do, please feel free to reply here and we
will follow up.

Thanks very much.

Sincerely,
Yanhong Huang
Microsoft Online Community Support

=============== =============== =============== =====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no rights.

[Walter Wang [MSFT]]

Hi Mark,

Sorry for late reply. I will do more research on your question and get back
to you as soon as possible. Thank you for your patience and understanding.
Regards,
Walter Wang (wa****@online. microsoft.com, remove 'online.')
Microsoft Online Community Support

=============== =============== =============== =====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no rights.

[Walter Wang [MSFT]]

Hi Mark,

If you set the "Debug Info" from "pdbonly" to "none", a required
DebuggableAttri bute is not emitted in the result assembly. Internally the
framework checks this attribute to determine whether or not to use the
DebuggableCallb ack instead of the normal Callback.

By default, a Release configuration has setting "pdbonly", it will only
emit some attribute in the assembly; you don't need to release the .pdb
file.

So the answer to your last question about whether or not it's a bug in IDE
is: it's not a bug in IDE. As I wrote in my first reply, this should still
be considered as by design.

Back to initial requirement, if your desire is to report the exception with
your own dialog, I think customizing the built-in exception dialog is the
way to go. You also don't need to put many try-catch block in your code.
Remember, this issue only applies to the event triggered by NativeWindow
(WndProc callback), normal program exceptions are not effected.
Regards,
Walter Wang (wa****@online. microsoft.com, remove 'online.')
Microsoft Online Community Support

=============== =============== =============== =====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no rights.

[Mark Lewis]

Thanks. As I said, I believe this is a bug as errors that are trapped in the
IDE by the normal Try-Catch syntax are not caught in an EXE unless the JIT
switch is set and a PDB is generated. The product should behave consistently
one way or the other. If this is by design then it is a silly design but I
suspect that this was never thought through carefully so is not by design.

It does appear that a custom error handler is the only way to trap these
sort of errors. Hopefully this will be fixed/redesigned in a later release.

I think you can close this one out as there does not seem to be any Hotfix
and there is a work around.

Thanks again,

Mark
"Walter Wang [MSFT]" <wa****@online. microsoft.comwr ote in message
news:HK******** ******@TK2MSFTN GXA01.phx.gbl.. .

Hi Mark,

If you set the "Debug Info" from "pdbonly" to "none", a required
DebuggableAttri bute is not emitted in the result assembly. Internally the
framework checks this attribute to determine whether or not to use the
DebuggableCallb ack instead of the normal Callback.

By default, a Release configuration has setting "pdbonly", it will only
emit some attribute in the assembly; you don't need to release the .pdb
file.

So the answer to your last question about whether or not it's a bug in IDE
is: it's not a bug in IDE. As I wrote in my first reply, this should still
be considered as by design.

Back to initial requirement, if your desire is to report the exception
with
your own dialog, I think customizing the built-in exception dialog is the
way to go. You also don't need to put many try-catch block in your code.
Remember, this issue only applies to the event triggered by NativeWindow
(WndProc callback), normal program exceptions are not effected.
Regards,
Walter Wang (wa****@online. microsoft.com, remove 'online.')
Microsoft Online Community Support

=============== =============== =============== =====
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=============== =============== =============== =====

This posting is provided "AS IS" with no warranties, and confers no
rights.