Error handling in .Net Remoting

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

suhas - 02 Nov 2006 10:06 GMT

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.

Please guide

Thanks
Suhas

Reply to this Message

Günter Prossliner - 02 Nov 2006 13:20 GMT

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.

The main problem is, that almost everything that might go wrong within
Remoting is signaled by the "RemotingException" class.

see my posting related to this topic:
http://groups.google.at/group/microsoft.public.dotnet.framework.remoting/browse_
thread/thread/ab5a06c30652d96/5674e74c3f231f6b

and the Feature-Request I have submitted to MS.
https://connect.microsoft.com/VisualStudio/feedback/ViewFeedback.aspx?FeedbackID
=175516

GP

Reply to this Message

Error handling in .Net Remoting

Free Magazines