Should I make my CustomException serializable?

Question

I'm defining a custom exception class to signal to my handler for a specific action to be taken. I'm wondering if I should make my exception Serializable or not. I don't intend to use the exception as anything more than an exit from my current execution.

(and yes, I do need a custom exception class. I'm pretty sure about that)

possible duplicate of [Why should I always make my Exceptions \[serializable\]? (.NET)](http://stackoverflow.com/questions/1066701/why-should-i-always-make-my-exceptions-serializable-net) — Tim Abell, Oct 08 '14 at 15:58

score 2 · Accepted Answer · answered Feb 05 '11 at 02:24

2

The best practice is to make them serializable. This way they can be serialized across AppDomain, or even process, boundaries.

answered Feb 05 '11 at 02:24

John Saunders

160,644
26
247
397

1

Microsoft guidelines on Custom Exception: [Designing Custom Exceptions](http://msdn.microsoft.com/en-us/library/ms229064.aspx) – Devendra D. Chavan Feb 05 '11 at 02:28
That comment contains a dead link now :-( – Tim Abell Oct 08 '14 at 15:55
Updated link (just changed the .net version to 4) http://msdn.microsoft.com/en-us/library/ms229064(v=vs.100).aspx – Tim Abell Oct 08 '14 at 15:56

Should I make my CustomException serializable?

1 Answers1