Combating Namespace Bloat With .Net XML Serialization

Anyone who has used the .Net XmlSerializers have surely encountered the dreaded namespace bloat which makes the serialized objects grow to ridiculous sizes.

There’s a nice little article over at TopXML on how to deal with this bloat.

If you’re using WSCF, on the client stub, I’ve gotten into the habit of writing custom serialization overrides in partial classes which ensure that if the client needs to serialize objects into XML, I’m doing so in an efficient manner.  It’d be nice to see it added to the server side class constructors as well.  Add your vote for this feature over at the WSCF dicussion boards.

You may also like...