Well that might be cause it an unusall situation, they problem would only show if there was a fault before the message is sent, if after sending i.e. if there is a server side failure the fault handling works becuase it doesnt run through the same mechanism of using the AsyncDispatcher.
So for us server fault are just great but client fault are the issue... But I will try and put together a demo --- In [email protected], Tom Chiverton <[EMAIL PROTECTED]> wrote: > > On Monday 06 Oct 2008, reflexactions wrote: > > Becuase its not the Operation that gets GC'd its the AsyncDispatcher > > that gets GC'd but without the AD the Fault handler will never get > > called. > > Well, no one else has this problem with the fault event handler, so you must > be doing something different/unusual. > Can you post a small self contained example ? > > -- > Tom Chiverton > Helping to administratively pursue viral content > > > > **************************************************** > > This email is sent for and on behalf of Halliwells LLP. > > Halliwells LLP is a limited liability partnership registered in England and Wales under registered number OC307980 whose registered office address is at Halliwells LLP, 3 Hardman Square, Spinningfields, Manchester, M3 3EB. A list of members is available for inspection at the registered office. Any reference to a partner in relation to Halliwells LLP means a member of Halliwells LLP. Regulated by The Solicitors Regulation Authority. > > CONFIDENTIALITY > > This email is intended only for the use of the addressee named above and may be confidential or legally privileged. If you are not the addressee you must not read it and must not use any information contained in nor copy it nor inform any person other than Halliwells LLP or the addressee of its existence or contents. If you have received this email in error please delete it and notify Halliwells LLP IT Department on 0870 365 2500. > > For more information about Halliwells LLP visit www.halliwells.com. >
