From the documentation I could find, it seems that reading “appSettingsâ €ť from
the app.config file is now done through ConfigurationMa nager.AppSettin gs for
..NET 2.0, instead of the obsolete ConfigurationSe tting.AppSettin gs. But
what’s kind of confusing is that “appSetttings ” itself seems to be in
disfavor. Accessing “applicationS ettings” using My.Settings seems to be the
preferred way.
1st question: Is My.Settings preferred to using ConfigurationMa nager?
But using My.Settings presents me with this problem. With “appSettingsâ €ť,
the code would always pull values from MyApp.exe.confi g. It did not matter
if the code were in the Exe or some DLL that it used. But now if I use
My.Settings.MyS etting (or My.Settings.Ite m(“MySettingâ €ť) in a non-typed way),
the code will attempt to pull it from the config of the assembly that it is
in. That is, if the code is in the Exe then it will look in
MyApp.exe.confi g, but if it in the DLL then it will look in MyLib.dll.confi g.
2nd question: Is there a “My.Settingsâ €ť way of accessing the config values of
the Executable from code that is in a referenced assembly?
I tried putting “MySetting” in both the app.config files for the Exe and
DLL. I hoped that the Exe value would override the DLL value, but it did not
work. The accessing code in the DLL only found values in MyLib.dll.confi g.
I guess I could resort to doing the semi-new way of using
ConfigurationMa nager to read “appSettingsâ €ť but I am hoping that there is a
general approach to using the Exe’s My.Settings that I haven’t found.
