+972 52-548-6969
Serialization Hurts Me
time to read 2 min | 207 words
I am now adding serialization support to Dynamic Proxy 2, and it is painful. It is painful because:
- I never did much with serialization, and there seem to be a lot of black magic there with regard to whatever you implement ISerializable, has [Serializable] or use any of the special hooks.
- I am working with serializaztion by directly manipulating the IL generation. This makes for fun debugging.
- Dyanmic Proxy needs a couple special serialization hooks in order to work properly, see the first point.
At this point, I feel like my head is spinning, but I think that the tests are passing...
Update: Seems that I spoke too soon, I am bravely discoverring new exceptions:
System.TypeLoadException : Could not load type 'ObjectProxyeefadda2f25c4dffafe2b0f3c2736c95' from assembly 'DynamicProxyGenAssembly2, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null' because it attempts to implement a class as an interface.
Comments
Are you going to document the gotchas so that others won't have to suffer quite as much as you? I've recently started doing this: http://luke.breuer.com/time/tag/gotcha.aspx . Look interesting?
No really, those are probably well documented.
My difficulties were with handling those via IL manipulation, not just serializaztion
Well documented in one or a few places, or well documented if I were to do "select distinct idea_fragment from Internet where topic = '.net serialization'"? Note that even a few gotchas can waste a lot of time.
Perhaps you would be interested in documenting your difficulties with IL manipulation so that others could use that knowledge?
Comment preview