c# - What are the cases that cause WCF proxy to be faulted? -


I should know in which case the WCF proxy (generated by vs2008 or svcutil) becomes defective state is? So I can recreate the new example and can not use the defective use.

Currently I'm dealing with the timeout exception, FaultException, CommunicationObjectAbortedException

  try {client.Method1 (args); } Hold (timeout Exception) {client.Abort (); Re: (); } FaultException {client.Abort (); Re: (); } Hold (communication object quote) {client.Abort (); Re: (); }  

I think I can escape from all these types and can only handle parental communication exceptions, is it enough? I need commenting

Any exception exception on the server side that is FaultException Or FaultException & lt; T & gt; will blame your channel In a per-call scenario or one-way scenario, you often do not care about the fault of the channel, but in a session-based scenario, you definitely!

Your best bet is to actually try and hold all the exceptions on the server side and either press them (log on to server and do nothing), or give them a FaultException Return on the road.

In order to do this, your implementation of the implementation of your service should also be implemented that allows you to do this - grab all the exceptions and either logging them +, or converting them into SOAP defects.

Mark


Comments

Popular posts from this blog

c# - ListView onScroll event -

PHP - get image from byte array -

Linux Terminal Problem with Non-Canonical Terminal I/O app -