c# - OpenMappedExeConfiguration 与 OpenExeConfiguration

Question

OpenExeConfiguration 有 2 个重载:

• ConfigurationManager.OpenExeConfiguration (ConfigurationUserLevel) ----- (1)
• ConfigurationManager.OpenExeConfiguration (String) ----- (2)

OpenMappedExeConfiguration 只有 1 个原型(prototype):

• OpenMappedExeConfiguration (ExeConfigurationFileMap fileMap,ConfigurationUserLevel userLevel) ----- (3)

似乎 (2) 和 (3) 都可以用来打开特定的配置文件，而不是默认的 app.config 文件。

那么它们有什么区别呢？什么时候使用哪个？

为什么我们在(1)和(2)中将UserLevel和Config File Location分开，而在(3)中将它们合并？

感谢您的任何回复。

更新

我知道微软总是喜欢以不止一种方式做事。但它应该这样做是有原因的。任何人都知道我的问题的原因吗？我们需要赏金 ;) 吗？

Answer 1

差异在最终的 .NET 配置资源中进行了解释 - Cracking the Mysteries of .NET 2.0 Configuration :

OpenExeConfiguration(字符串)

will append ".config" to the filename you provide and load that configuration file. It's important to note that OpenExeConfiguration(string exePath) is a very misleading method, as the filename does not have to be the filename of the .exe that is running [...] By providing a filename other than the EXE filename, an alternate *.config file can be opened.

OpenExeConfiguration (ConfigurationUserLevel)

The second method, OpenExeConfiguration(ConfigurationUserLevel level) will load the appropriate configuration file for the specified configuration level. Configuration levels, available in the Exe context, allow you to specify whether you want exe, roaming user, or local user configuration [...] Remember that configuration is hierarchical and merged. When requesting roaming or local user configuration, that level up through machine.config are merged, resulting in the complete configuration accessible by your application for the given user level.

OpenMappedExeConfiguration()、OpenMappedMachineConfiguration()

Unlike the OpenExeConfiguration() methods, which make several assumptions about where your configuration files reside, OpenMappedExeConfiguration() and OpenMappedMachineConfiguration() allow you to explicitly specify where your *.config files reside on disk. Using these methods, you can load an alternate machine.config, load User.config files from the locations of your own choosing (vs. letting the .NET framework decide on some convoluted path), etc. When accessing machine.config, a custom version is not required, OpenMachineConfiguration() should be used instead.