Undocumented configuration setting for XmlSerializer - and a new question emerges?
Doug Purdy inspired the crowd just to test (if there were such a possible setting) what would happen if you do this here in an application which uses XmlSerializer.
Very cool! If you do not want to try it out by yourself then I would recommend to download this little test program ;-) [Christian Weyer]
Now that's COOL. Nice to get that insight into what's going on inside the XmlSerializer.
<sidenote>Recognize that filenaming style? "qhtozc7m.0.cs" and "qhtozc7m.cmdline"? You may have seen it in c:/WINDOWS/Microsoft.NET/Framework/v1.0.3705/Temporary ASP.NET Files. (If you haven't, go look!</sidenote>
So, now my question to the people is, what .NET Framework subsystem is managing all those temporary files, lifetime, naming, launching csc.exe, etc, for this kind of compilation? CodeDOM? Don't think so...