System.Windows.Forms.ApplicationConfigurationSection破坏了旧版本.net的web.config中的破坏 [英] System.Windows.Forms.ApplicationConfigurationSection wrecking havoc in web.config for older .net versions

问题描述

有人(不是我)将此添加到了Stack Overflow:

Someone (not me) added this to Stack Overflow:

https://stackoverflow.com/questions/44764032/net-4-7-invalid-configsection-added-to-web-config

https://stackoverflow.com/questions/44764032/net-4-7-invalid-configsection-added-to-web-config

我也遇到了同样的问题，因为他解释得很好，所以我链接到他的问题.

I'm running into the same issue, and since he explained it so well there I am linking to his question.

我想问的是:

这是它应该如何工作的意图，还是一个错误?

Is this the intention of how it should work, or is it a bug?

使用这种与web.config一起使用的方式的我们是否应该开始研究重写我们的web.config管理代码，或者这是我们可以期望在许多客户开始升级到.net 4.7之前迅速修复的错误? /p>

Should we who use this way of working with web.config start looking into rewriting our web.config management code, or is this a bug that we can expect a fix on quickly before many customers start upgrading to .net 4.7?

推荐答案

KjellAhlstrom，您好

Hi KjellAhlstrom,

谢谢您在这里发布.

对于您的问题，您可以修改 appsettings  元素

For your question, you could modify the appsettings element to reference an external file using the <appSettings file="path to file"/> syntax. When programmatically updating that external xml file, the issue is not triggered.

有关详细信息，请参见以下链接.

https://github.com/Microsoft/dotnet/issues/435

最好的问候，

温迪

这篇关于System.Windows.Forms.ApplicationConfigurationSection破坏了旧版本.net的web.config中的破坏的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！