CATCH block - but .NET execption is shown in OE ALERT-BOX

It's working as expected within Win7 development, the .NET exeptions (like paper empty, cover open) are thrown and catched by "catch pce as Microsoft.PointOfService.PosControlException" within PrintReceipt.

...
 
I have no idea why CATCH doesn't catch ...

Maybe the older OPOS Drivers raise a different exception?

Try CATCHing the general System.Exception instead of the PosControlException and try to output the GetType():FullName.

Maybe the error class name is actually the same, but the fully qualified name (including version, culture and public key token of the vendor) are not the same I could in principle imagine that without proper assembly probing the PosControlException thrown and the PosControlException expected by your CATCH block are not the same (in this case the Assembly version present during compilation would be expected).

Mike,

thanks for you hint, i will check this.

An external consultant ( ;-) ) added this to our application:

"catch ple as Progress.Lang.Error"

Until today i thought that this is the "ultimative CATCH" in ABL.NET or do i need a second catch for System.Exception?

Teh used assemblies from POS for .NET 1.12 are unchanged since the beginning of this project.
BTW: Unfortunately MS seems to have no interest updating this and no one in the OpenEdge world seems to use it.

This is 1:1 in the the ABL Alert-Box:

Microsoft.PointOfService.PosControlException: Method OpenDrawer threw an excecption.

The device can not perform the requested procedure.

This is 100% the exception that is in my CATCH block.

Stefan

Hi Stefan:

You are correct, ... the ultimate CATCH ("catch ple as Progress.Lang.Error") should catch all errors.  You should log a call with Technical Support for this issue.

This is was i did this afternoon.

Technical Support found this "limitation" in the docs:

---------------------------------------------------------------------------------------------------

Raising errors from ABL handlers for .NET events When a .NET event is published to which you have subscribed ABL handlers (see the “Handling .NET events” section on page 2–35), if an error condition is raised from an ABL handler for the .NET event, the AVM does not throw an Exception to the .NET Common Language Runtime (CLR), but displays a message to the default output device and processing continues as if no error has occurred. Thus, if any handlers for the event have not yet run when a handler raises an error, all remaining handlers continue to run. Note: This is different from the AVM response to an error condition raised from a handler for an ABL class event. In this case, the AVM raises the error on the statement that invoked the ABL Publish( ) method on the event, and any handlers that have not yet run for the event when the error is raised do not run.

---------------------------------------------------------------------------------------------------

I can't noticed this behaviour:"and processing continues as if no error has occurred".

But now i have to catch the error in the ABL handler and "save it" anywhere for later use. (i use DialogResult as a flag for an catched error)

That's not the error handling i learned with ABL.NET or C# but it works.

OT:

Posted with IE10/Win7, first i loosed all formats of the text.

Editing solves this problem but during any edit i am loosing parts of the message (IE10 bug or Progress bug?)