All exceptions should be serializable

[GoogleCodeExporter]

It is required for them to pass AppDomain boundaries

Original issue reported on code.google.com by lostfree...@gmail.com on 30 May 2012 at 8:44

[GoogleCodeExporter]

Original comment by stephen....@gmail.com on 30 May 2012 at 12:25

• Changed state: Accepted

[GoogleCodeExporter]

The two offending custom exception classes are EvaluationException and 
AssertionFailedException. 

We note the following resources for properly implementing serializable 
exceptions:

http://stackoverflow.com/questions/94488/what-is-the-correct-way-to-make-a-custo
m-net-exception-serializable
http://msdn.microsoft.com/en-us/library/ms229064.aspx

We note the following F# language resources (regarding inheriting multiple base 
class constructors, and F#'s lack of protected access):

http://stackoverflow.com/questions/1619567/f-type-inheritance
http://www.atalasoft.com/cs/blogs/stevehawley/archive/2010/08/10/using-a-proxy-c
lass-to-fix-f-protected-access-limitation.aspx

Original comment by stephen....@gmail.com on 31 May 2012 at 1:53

[GoogleCodeExporter]

Note that Silverlight 4 doesn't support serialization (for example, see that 
the "Other versions" of SerializationAttribute doesn't include any version of 
Silverlight: 
http://msdn.microsoft.com/en-us/library/system.serializableattribute.aspx).

Original comment by stephen....@gmail.com on 31 May 2012 at 2:11

[GoogleCodeExporter]

This issue was closed by revision r584.

Original comment by stephen....@gmail.com on 31 May 2012 at 2:12

• Changed state: Fixed

[GoogleCodeExporter]

Original comment by stephen....@gmail.com on 15 Jun 2012 at 12:57

• Added labels: Milestone-Release2.2.2