In my remoting object, I do the following to pass the exception back up to the client:
Catch ex As Exception
Throw ex
An exception is thrown back to the client indeed, but the exception message is not being passed. For example, in the remoting object, if I put a breakpoint on the Throw ex, I see a message of 'record exists'.
On the client, I just see errors such as 'the server has thrown an exception', 'the target of invocation has etc.'.
Shouldn't the Exception class be able to throw an exception back to the client?
STom
Liju Thomas [MS] - 03 Jul 2003 01:22 GMT
Once you catch the exception, try creating a RemotingException with the details and throw it.

Signature
thanks,
liju
This posting is provided "AS IS" with no warranties, and confers no rights.
In my remoting object, I do the following to pass the exception back up to the client:
Catch ex As Exception
Throw ex
An exception is thrown back to the client indeed, but the exception message is not being passed. For example, in the remoting object, if I put a breakpoint on the Throw ex, I see a message of 'record exists'.
On the client, I just see errors such as 'the server has thrown an exception', 'the target of invocation has etc.'.
Shouldn't the Exception class be able to throw an exception back to the client?
STom