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

unhandled exception error during release, but not development

P: n/a
What factor would allow an unhandled exception to occur in a compiled
project, versus no error for the same action during development? In other
words, I have a project that, in development when I test it, runs no
problem. When I compile and release the dll, the user gets an unhandled
exception. It doesn't halt the code, it just shows an error dialog...click
continue and it continues.

Is there some setting I must set so that I can see these during development?

Thanks.
Feb 23 '07 #1
Share this Question
Share on Google+
5 Replies


P: n/a
I'm just a beginner so take this with a grain of salt:
use the Err.Number and Err.Discripion for several of the posible exceptions
to find out what the problem is by sending the results to a MsgBox?

Randy

"Tim Zych" <FirstInitial+LastName@earth_LinkDotNetwrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl...
What factor would allow an unhandled exception to occur in a compiled
project, versus no error for the same action during development? In other
words, I have a project that, in development when I test it, runs no
problem. When I compile and release the dll, the user gets an unhandled
exception. It doesn't halt the code, it just shows an error dialog...click
continue and it continues.

Is there some setting I must set so that I can see these during
development?

Thanks.


Feb 23 '07 #2

P: n/a
The problem is not finding out what unhandled exception occurred. It's that
the exception is raised by the compiled (released) DLL, but not in
development mode.

I'm trying to learn why the IDE won't return the unhandled exception, but
the compiled application will.
"Randy" <ac***@comcast.netwrote in message
news:D8******************************@comcast.com. ..
I'm just a beginner so take this with a grain of salt:
use the Err.Number and Err.Discripion for several of the posible
exceptions
to find out what the problem is by sending the results to a MsgBox?

Randy

"Tim Zych" <FirstInitial+LastName@earth_LinkDotNetwrote in message
news:%2****************@TK2MSFTNGP05.phx.gbl...
>What factor would allow an unhandled exception to occur in a compiled
project, versus no error for the same action during development? In other
words, I have a project that, in development when I test it, runs no
problem. When I compile and release the dll, the user gets an unhandled
exception. It doesn't halt the code, it just shows an error
dialog...click continue and it continues.

Is there some setting I must set so that I can see these during
development?

Thanks.



Feb 23 '07 #3

P: n/a
Tim Zych wrote:
What factor would allow an unhandled exception to occur in a compiled
project, versus no error for the same action during development? In other
words, I have a project that, in development when I test it, runs no
problem. When I compile and release the dll, the user gets an unhandled
exception. It doesn't halt the code, it just shows an error dialog...click
continue and it continues.

Is there some setting I must set so that I can see these during development?

Thanks.
When the code is compiled in release mode it's more optimised. The code
compiled in debug more does for example contain a lot of NOP (no
operation) instructions as placeholders for debugging breakpoints, which
are not included in the relase mode.

It's possible that you have an error in your code that doesn't result in
an exception in debug mode but does in release mode. (It's also possible
that it's the result of an error in the compiler, but that is much less
likely.)

--
Göran Andersson
_____
http://www.guffa.com
Feb 24 '07 #4

P: n/a
Interesting...so I suppose the "best" way for me to test changes to a
solution, based on this experience, is outside the IDE.
Thanks for the feedback.

"Göran Andersson" <gu***@guffa.comwrote in message
news:%2****************@TK2MSFTNGP06.phx.gbl...
Tim Zych wrote:
>What factor would allow an unhandled exception to occur in a compiled
project, versus no error for the same action during development? In other
words, I have a project that, in development when I test it, runs no
problem. When I compile and release the dll, the user gets an unhandled
exception. It doesn't halt the code, it just shows an error
dialog...click continue and it continues.

Is there some setting I must set so that I can see these during
development?

Thanks.

When the code is compiled in release mode it's more optimised. The code
compiled in debug more does for example contain a lot of NOP (no
operation) instructions as placeholders for debugging breakpoints, which
are not included in the relase mode.

It's possible that you have an error in your code that doesn't result in
an exception in debug mode but does in release mode. (It's also possible
that it's the result of an error in the compiler, but that is much less
likely.)

--
Göran Andersson
_____
http://www.guffa.com


Feb 24 '07 #5

P: n/a
Interesting...so I suppose the "best" way for me to test changes to a
solution, based on this experience, is outside the IDE.
Thanks for the feedback.

"Göran Andersson" <gu***@guffa.comwrote in message
news:%2****************@TK2MSFTNGP06.phx.gbl...
Tim Zych wrote:
>What factor would allow an unhandled exception to occur in a compiled
project, versus no error for the same action during development? In other
words, I have a project that, in development when I test it, runs no
problem. When I compile and release the dll, the user gets an unhandled
exception. It doesn't halt the code, it just shows an error
dialog...click continue and it continues.

Is there some setting I must set so that I can see these during
development?

Thanks.

When the code is compiled in release mode it's more optimised. The code
compiled in debug more does for example contain a lot of NOP (no
operation) instructions as placeholders for debugging breakpoints, which
are not included in the relase mode.

It's possible that you have an error in your code that doesn't result in
an exception in debug mode but does in release mode. (It's also possible
that it's the result of an error in the compiler, but that is much less
likely.)

--
Göran Andersson
_____
http://www.guffa.com


Feb 24 '07 #6

This discussion thread is closed

Replies have been disabled for this discussion.