That is an enigmatic title to write about serialization. Well, sort of, as one of the meanings of the word refers to that concept.
But writing about successions is not my intention. My intention is to write about the technique that allows objects to be persisted to another medium different from their native memory space and more specifically on how to test serialization of objects.
Sure not many people know what a Zune player is (and even less own one).
But those who know it and are more or less up to date on what is going on in the Microsoft arena keep reminding me “oh… and by the way, your Zune is dead. Microsoft killed it.”
The other day I read an interesting post about testing and a library that might help in some cases, its title is “Introducing the Expected Objects” library. I thought it might be useful and so I spent a spare evening writing some code to check whether is something that could be useful for my team.
Yup, as I mentioned before, after the first “full release” of Testing.Commons, Testing.Commons.NUnit would start to receive more love (and code commits, now that we are at it).
The first version (0.1) has been released. Binaries can be downloaded from NuGet.
Let’s throw a party!
I am not going to start another flame war about whether documentation is evil or not.
My personal stand is that is evil but mostly needed.