I will discuss with you the issue of configurationmanager. openexeconfiguration (exepath ).

I <talk about additional configuration file reading and configrationmanager again. after posting the blog of openexeconfiguration (exepath) misleading error>, some friends put forward different opinions that this is not a bug, but a different understanding of the exepath parameter, then let me talk about my views. (In my opinion, this should be a bug)

I personally think: If exepath is the path of the EXE file, it will first generate another bug, that is, a translation error. On msdn, it is clearly pointed out that this is the path of the EXE configuration file, if it is the path of the EXE, the translation is wrong.

Second, will it be the path of EXE? I personally think it should not be the path of exe.Because the maximum significance of the configurationmanager. openexeconfiguration method is to open the custom Additional configuration file.The configuration. config file is not called an additional configuration file.

If any handsome guy has other methods for reading Additional configuration files, please kindly advise. I believe you will also need such practical things.

In addition, if the handsome guy has a more authoritative explanation and operation instructions for this method, or other examples of using this method in detail, he hopes to post them for discussion, I personally think that some changes to the configuration file are messy during the upgrade of the DOTNET framework. Now many new users do not know how to use it. I hope you can discuss more and share your experience. After all, the configuration file is used by various projects. Sorry, I am sorry.