Scott Hanselman

Undocumented configuration setting for XmlSerializer - and a new question emerges?

February 19, 2003 Comment on this post [0] Posted in Web Services | ASP.NET | XmlSerializer
Sponsored By

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...

About Scott

Scott Hanselman is a former professor, former Chief Architect in finance, now speaker, consultant, father, diabetic, and Microsoft employee. He is a failed stand-up comic, a cornrower, and a book author.

facebook twitter subscribe
About   Newsletter
Hosting By
Hosted in an Azure App Service

Comments are closed.

Disclaimer: The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.