Re: Error handling in .Net Remoting
- From: "Günter Prossliner" <g.prossliner/gmx/at>
- Date: Thu, 2 Nov 2006 13:20:08 +0100
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
.
- References:
- Error handling in .Net Remoting
- From: suhas
- Error handling in .Net Remoting
- Prev by Date: Error handling in .Net Remoting
- Next by Date: Question about data size when using serialized writing using BinaryFormatter
- Previous by thread: Error handling in .Net Remoting
- Next by thread: Question about data size when using serialized writing using BinaryFormatter
- Index(es):