How to handle WCF service error in Silverlight when session authentication timeout

Question

I have a WCF service that I am accessing in Silverlight. Silverlight application requires authentication (authentication occurs when a service is called.)

I noticed that when the authenticated session ends, and the user does something on the side of the application that will make the call to this service, the application simply freezes, waiting for a response from the service. My service is designed to throw an exception in these cases, however, nothing is assigned on the Silverlight side, and an exception occurs instead:

CommunicationException was not handled by user code

The remote server returned an error: NotFound.

In my maintenance methods, I check if the user is still checked, and if so, I continue the operation. If not, I assign a value to the output parameter (of type Exception). On the Silverlight side, I check to see if this exception is null, and otherwise take appropriate action. When I execute, the out parameter gets the correct exception, but then Silverlight throws the exception above (in Reference.cs) before it even gets to the point where I can handle it ...

Has anyone else seen this? Any suggestions?

. , , , . - Exception ( System.Exception)

Answer 1

:

WCF- , , ?

WCF Silverlight, ?

WCF Silverlight? , . , , .

Answer 2

WCF , . , , , "NotFound". , WCF:
http://msdn.microsoft.com/en-us/library/ms730064.aspx

Answer 3

-, , , : WCF Silverlight

, Silverlight 400 , , .

, , , , , . , ... - ?

Answer 4

:

Random "Not Found" Silverlight - ASP.NET

asmx, WCF. WCF silverlight. 404 .

Answer 5

WCF, , (. http://msdn.microsoft.com/en-us/library/dd470096(VS.95).aspx), - 404 - , .

, 2 :

• WCF, , .

• WCF, , App.xaml.cs:

  HttpWebRequest.RegisterPrefix( "https://", WebRequestCreator.ClientHttp); HttpWebRequest.RegisterPrefix( "http://", WebRequestCreator.ClientHttp); `

, Silverlight, 404.

Obviously, the transition to the client’s network stack has its drawbacks (for example, you will have to process authentication, caching, cookies yourself)