Databases
StackOverflow2013
Postsdbo
POWP7: Unable to catch FaultException in asynchronous calls to WCF service
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWP7: Unable to catch FaultException in asynchronous calls to WCF service
    primarykey
    data
    text
    <p>I am currently developing a Windows Phone 7 App that calls a WCF web service which I also control. The service offers an operation that returns the current user's account information when given a user's login name and password:</p> <pre><code>[ServiceContract] public interface IWindowsPhoneService { [OperationContract] [FaultContract(typeof(AuthenticationFault))] WsAccountInfo GetAccountInfo(string iamLogin, string password); } </code></pre> <p>Of course, there is always the possibility of an authentication failure and I want to convey that information to the WP7 app. I could simply return null in that case, but I would like to convey the reason why the authentication failed (i.e. login unknown, wrong password, account blocked, ...).</p> <p>This is my implementation of the above operation (for testing purposes, all it does is throwing an exception):</p> <pre><code>public WsAccountInfo GetAccountInfo(string iamLogin, string password) { AuthenticationFault fault = new AuthenticationFault(); throw new FaultException&lt;AuthenticationFault&gt;(fault); } </code></pre> <p>Now, if I call this operation in my WP7 app, like this:</p> <pre><code>Global.Proxy.GetAccountInfoCompleted += new EventHandler&lt;RemoteService.GetAccountInfoCompletedEventArgs&gt;(Proxy_GetAccountInfoCompleted); Global.Proxy.GetAccountInfoAsync(txbLogin.Text, txbPassword.Password); void Proxy_GetAccountInfoCompleted(object sender, RemoteService.GetAccountInfoCompletedEventArgs e) { if (e.Error != null) { MessageBox.Show(e.Error.Message); return; } } </code></pre> <p>The debugger breaks in Reference.cs, saying that FaultException'1 was unhandled, here: </p> <pre><code>public PhoneApp.RemoteService.WsAccountInfo EndGetAccountInfo(System.IAsyncResult result) { object[] _args = new object[0]; PhoneApp.RemoteService.WsAccountInfo _result = ((PhoneApp.RemoteService.WsAccountInfo)(base.EndInvoke("GetAccountInfo", _args, result))); return _result; } </code></pre> <p><strong>BEGIN UPDATE 1</strong></p> <p>When pressing F5, the exception bubbles to:</p> <pre><code>public PhoneApp.RemoteService.WsAccountInfo Result { get { base.RaiseExceptionIfNecessary(); // &lt;-- here return ((PhoneApp.RemoteService.WsAccountInfo)(this.results[0])); } } </code></pre> <p>and then to:</p> <pre><code>private void Application_UnhandledException(object sender, ApplicationUnhandledExceptionEventArgs e) { if (System.Diagnostics.Debugger.IsAttached) { // An unhandled exception has occurred; break into the debugger System.Diagnostics.Debugger.Break(); } } </code></pre> <p>After that, the app terminates (with or without the debugger).</p> <p><strong>END UPDATE 1</strong></p> <p>Now, I would love to catch the exception in my code, but I am never given the chance, since my Completed handler is never reached. </p> <p>Based on similar questions on this site, I have already tried the following:</p> <ul> <li>Re-add the service reference --> no change</li> <li>Re-create a really simple WCF service from scratch --> same problem</li> <li>Start the app without the debugger to keep the app from breaking into the debugger --> well, it doesn't break, but the exception is not caught either, the app simply exits</li> <li>Tell VS 2010 not to break on FaultExceptions (Debug > Options) --> does not have any effect</li> <li>wrap every line in my app in try { ... } catch (FaultException) {} or even catch (Exception) --> never called.</li> </ul> <p><strong>BEGIN UPDATE 2</strong></p> <p>What I actually would like to achieve is one of the following:</p> <ul> <li><p>ideally, reach GetAccountInfoCompleted(...) and be able to retrieve the exception via the GetAccountInfoCompletedEventArgs.Error property, or</p></li> <li><p>be able to catch the exception via a try/catch clause</p></li> </ul> <p><strong>END UPDATE 2</strong></p> <p>I would be grateful for any advice that would help me resolve this issue.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USChris Leesch
    1. USChris Leesch
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWP7: Unable to catch FaultException in asynchronous calls to WCF service
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWP7: Unable to catch FaultException in asynchronous calls to WCF service
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWP7: Unable to catch FaultException in asynchronous calls to WCF service
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI see that you got the exception in the `EndGetAccountInfo` method, but did you try to press F5 to keep the code running and see if the `Proxy_GetAccountInfoCompleted` was called with the exception info?
      singulars
      1. POWP7: Unable to catch FaultException in asynchronous calls to WCF service
      1. USPedro Lamas
    2. COI have updated the question to include what happens after pressing F5. The exception ends up in the app's Application_UnhandledException handler.
      singulars
      1. POWP7: Unable to catch FaultException in asynchronous calls to WCF service
      1. USChris Leesch
    3. COCheck the proxy class if the methods are marked with `[System.ServiceModel.XmlSerializerFormatAttribute(SupportFaults=true)]`
      singulars
      1. POWP7: Unable to catch FaultException in asynchronous calls to WCF service
      1. USPedro Lamas
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload