Error handling in .Net Remoting

[suhas]

Hi
We have .net remoting applications (using .net framework 1.1)
I want to implement error handling in much better way to conclude about
the problem/failure occurred.

What are the standard or Microsoft recommendations when communication
fails due to several reasons like

Server or Client hangs
Server or Client machine is not up
Network communication error

Is there any standards recommended from Microsoft to catch the errors
and follow all over the application.


Thanks
Suhas

 

[Laurent Bugnion]

Hi,

Hi
We have .net remoting applications (using .net framework 1.1)
I want to implement error handling in much better way to conclude about
the problem/failure occurred.

What are the standard or Microsoft recommendations when communication
fails due to several reasons like

Server or Client hangs
Server or Client machine is not up
Network communication error

Is there any standards recommended from Microsoft to catch the errors
and follow all over the application.


Thanks
Suhas

When these scenarios occur, an exception will be thrown. If the server
machine is not there, for example, a SocketException is thrown. The
exception message informs you about the reason for the error, for
example "Target machine actively refused the connection" (or something
similar, sorry, working from memory here).

The nice thing with this model is that exceptions thrown on the server
are also serialized and passed to the client. So you can implement
different try...catch handlers to deal with the different exceptions, or
have one general exception handler to inform the client about the
failure, log it, etc...

I am not aware of specific guidelines regarding this, apart from the
normal exceptions guidelines.

HTH,
Laurent