P
Phil Jones
I've got a really weird little thing going on!
I've got a simple little win-forms project that is referencing some class
libraries.
When I write a Try/Catch block within the win-forms project, and an
exception is raised within the class-library the error isn't handled by my
Try/Catch, rather processing stops at the exception within class-library.
eg.
1 Try
2
3 myClassFromOtherAssembly.DoSomethingWithError()
4
5 Catch ex As Exception : msgbox (ex.ToString)
6 End Try
VS.NET launches into the debugger at line 3 displaying the class within the
other assembly where the error was initially thrown - it never gets handled
by my Try/Catch.
The VS.NET Debug ==>/ Exceptions settings are the default in all projects
concerned.
Never seen that before. Is just this Monday morning stupidity???? Does
anyone have a suggestion, or seen this happen before?
Cheers.
===
Phil
I've got a simple little win-forms project that is referencing some class
libraries.
When I write a Try/Catch block within the win-forms project, and an
exception is raised within the class-library the error isn't handled by my
Try/Catch, rather processing stops at the exception within class-library.
eg.
1 Try
2
3 myClassFromOtherAssembly.DoSomethingWithError()
4
5 Catch ex As Exception : msgbox (ex.ToString)
6 End Try
VS.NET launches into the debugger at line 3 displaying the class within the
other assembly where the error was initially thrown - it never gets handled
by my Try/Catch.
The VS.NET Debug ==>/ Exceptions settings are the default in all projects
concerned.
Never seen that before. Is just this Monday morning stupidity???? Does
anyone have a suggestion, or seen this happen before?
Cheers.
===
Phil