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
