We've found that Exceptions don't always serialize friendly. The actual exception likely has something that would require serialization by reference, or would require inspecting attributes for things to ignore which isn't supported. I would recommend trying to simplify the Exception into a DTO for the exception information you care about. If that doesn't work for you there are hooks to provide your own serialization for certain types.
On Wed, Mar 9, 2011 at 6:20 AM, Dirk Schuermans <[email protected]>wrote: > This is the following message that should be sent with the .Reply() > > using System; > > namespace Data.Messages.Admin > { > public class AgentActivated > { > public string Agent { get; set; } > public Exception Exception { get; set; } > > } > } > > Also , when there is no exception at all during the first try-catch, > the second one will not result in a StackOverflowException > Only when there's an exception in the first try-catch there will be a > StackOverflowException during the second one > > On 9 mrt, 14:16, Corey Kaylor <[email protected]> wrote: > > What is the message that it's trying to serialize? > > -- > You received this message because you are subscribed to the Google Groups > "Rhino Tools Dev" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/rhino-tools-dev?hl=en. > > -- You received this message because you are subscribed to the Google Groups "Rhino Tools Dev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rhino-tools-dev?hl=en.
