xmlserializer_XmlSerializer的未记录的配置设置-出现一个新问题？

xmlserializer

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]

道格·普迪( Doug Purdy)启发了人群，只是测试(如果有这样的可能)，如果您在使用XmlSerializer的应用程序中执行此操作，将会发生什么。 很酷！ 如果您不想自己尝试，那么我建议您下载这个小测试程序；-) [ Christian Weyer ]

Now that's COOL.  Nice to get that insight into what's going on inside the XmlSerializer. 

现在很酷。 很高兴了解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>

< sidenote >识别这种文件命名样式吗？ “ qhtozc7m.0.cs”和“ qhtozc7m.cmdline”？ 您可能已经在c：/WINDOWS/Microsoft.NET/Framework/v1.0.3705/Temporary ASP.NET文件中看到它。 (如果没有，请看看！ </ 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...

因此，现在我的问题是，对于这种编译，哪个.NET Framework子系统正在管理所有这些临时文件，生存期，命名，启动csc.exe等？ CodeDOM？ 别这样...

翻译自: https://www.hanselman.com/blog/undocumented-configuration-setting-for-xmlserializer-and-a-new-question-emerges

xmlserializer