Hi,
After all these years I have encountered this problem where exceptions were handled differently.
Martin wrote about X++ and CIL.
http://dev.goshoom.net/en/2013/09/exception-handling-with-x-and-net-interop/
I wrote a custom web service with try/catch statements to see how it behaves.
After debugging I found it errored with unhandled ErrorException.
The calling .NET console app catches the error as System.ServiceModelCommunicationException. This has the first error.
The fact that AX does not respect the "catch" concerns me. What this is telling me is that I have to make my web service much more granular. Also, catching the errors in the calling application and dealing with it.
I wanted to see if others are experiencing the same or if any comments.
*This post is locked for comments