why do you think the serialized objects are larger than they should be? how are you serializing?
also, you can write custom serialization routines (look at GetObjectData methods)
Since we do not have access to the binary format, there is no easy way to detemine what data is in the file. It sure would be nice if we at least had a dump utility for the binary format so that we could peer inside the file (I'm not sure why Microsoft feels the need to keep the format so closely guarded). If you are lucky and only using the functionality provided by one of the human readable formats, you might be able to output your data in one of those formats and look at the contents but In my experience, there aren't two serialization models compatible enough to do so.
The only option I can think of other than tracing is to write your own formatter so that the data is readable and/or dumpable.
- Ray
you can always serialize out to xml when looking for these... the soap formatter is useful somethimes (although verbose)...
See http://members.microsoft.com/consent/info/TaskDetails.aspx?pkid=920.
- Ray
I am glad to see this licensing available, but do wonder under what circumstances would a private consultant/developer benefit from obtaining such a license (e.g. if I write a simple Tcp Client/Server system for someone to use on an intranet, do I need to obtain a license or does my VS license cover this use?)
I doubt anyone would sign this license just so they can peek inside the binary format to see what they serialized. At least I know I won't.
A converter from the binary format to human readable/xml would still be a nice tool to have.
- Ray
RayManning wrote:
A converter from the binary format to human readable/xml would still be a nice tool to have.
