We used BinarySerialization with our C # application, but the size and complexity of the classes that need to be serialized leads to serialization of sloooooow (de) and large files.
We suspect that we should simply write our own serializers; but protobuf-net requires significant speed and size advantages over standard .Net binary serialization and it may be easier to add to our application than a large number of custom serializers.
Before I spend considerable time and effort on getting him to work for us, I would like to know if there are any deals. We use properties defined with interfaces, general lists of abstract subclasses, custom flag flags, etc. Etc. What would stop protobuf-net for us?
source
share