I'm using Daniel Vaughan Loggin and have been quite happy so far. We were already using Log4Net in the server, so it fitted pretty well. We needed to do some tricks to implement it since the article in CodeProject. If you are interested I can send you more information on how we did it (sorry I don't have it at hand at the moment).
Implementing an offline functionality should be somewhat straight forward. For offline scenarios, I ported the Disconnected Service Agent from P&P used in the Mobile Client Software Factory to allow to temporarily save service requests in queue and dispatch them when a connection is available. This pattern works pretty well for atomic services that doesn't block the functionality or when an application is completely designed to support Offline Scenarios, which isn't the case for must SL apps, specially not having an local DB. RIA Services uses a similar approach, but works on Domain/Service Context instead of at a Service Operation level. On Mon, May 25, 2009 at 1:02 PM, John OBrien <[email protected]>wrote: > Since the majority of errors we have so far are actually WCF > communication errors this would make a lot of sense. Plus for power users > we can always get the logs manually. Thanks. > > > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Gilbert Corrales > *Sent:* Monday, 25 May 2009 12:54 PM > *To:* [email protected] > *Subject:* Re: Exception handling / reporting RIA > > > > maybe a hybrid between isolated storage and remote error handling could > work... in the case of error reporting the error we can log it temporary in > isolated storage and later when the connection is reestablished we can log > any information left > > might do for an interesting experiments. > > On Mon, May 25, 2009 at 11:14 AM, John OBrien <[email protected]> > wrote: > > Has anyone come across a good architecture for handling exceptions in > Silverlight gracefully? > > Ideally we want the user to get something generic but for the full error to > be logged, since Silverlight runs on the client I assume we would need to > implement a WCF service for error reporting? > > > > And clearly we don’t want an error to happen in the error handler itself, > it needs to be very robust. Any pointers? > > > > John. > ------------------------------ > > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: http://www.codify.com/lists/ozsilverlight > Other lists you might want to join: http://www.codify.com/lists > > > ------------------------------ > > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: http://www.codify.com/lists/ozsilverlight > Other lists you might want to join: http://www.codify.com/lists > ------------------------------ > Support procedure: https://www.codify.com/lists/support > List address: [email protected] > Subscribe: [email protected] > Unsubscribe: [email protected] > List FAQ: http://www.codify.com/lists/ozsilverlight > Other lists you might want to join: http://www.codify.com/lists > -- Miguel A. Madero Reyes www.miguelmadero.com (blog) [email protected] -------------------------------------------------------------------------------- Support procedure: https://www.codify.com/lists/support List address: [email protected] Subscribe: [email protected] Unsubscribe: [email protected] List FAQ: http://www.codify.com/lists/ozsilverlight Other lists you might want to join: http://www.codify.com/lists
