Preserve exception stack trace does not handle non-serializable exceptions

[SimonCropp]

If an exception is thrown that does not properly implement ISerilizable we cannot preserve the stack trace. As in it will throw a SerializationException

An example of how to "not properly implement ISerilizable" is forgetting to add the custom contructor

protected MyException(SerializationInfo info, StreamingContext context)

so you exception would look like this

public class MyException: Exception
{
}

This should be fairly rare since it is one of the exception design guidelines http://msdn.microsoft.com/en-us/library/vstudio/ms229064(v=vs.100).aspx

Do make exceptions serializable. An exception must be serializable to work correctly across application domain and remoting boundaries.

The workaround

If this is happening to people during development the easiest way to diagnose the underlying issue is to use "Break on all exceptions" http://msdn.microsoft.com/en-us/library/vstudio/d14azbfh.aspx

[SimonCropp]

fixed in d761b0e