1

I'm writing a .NET DLL (C#) that is an add-in for a 3rd party product. That product includes this in it's application.exe.config file:

<startup useLegacyV2RuntimeActivationPolicy="true">
  <supportedRuntime version="v4.0"/>
</startup>

My DLL targets .NET v3.5, and my app.config file includes this:

<configSections>
  <sectionGroup name="userSettings" type="System.Configuration.UserSettingsGroup, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >
  <section name="myDLL.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" />
  </sectionGroup>
</configSections>

When I use the Settings object (derived from ApplicationsSettingsBase) to save a setting, the save works - and the data is saved to the user.config file of the host application. However, it is saved with this in it (note the Version=4.0.0.0):

<configSections>
  <sectionGroup name="userSettings" type="System.Configuration.UserSettingsGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" >
    <section name="myDLL.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" />
    <section name="anotherVendorsDLL.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" />
  </sectionGroup>
</configSections>

With these settings saved, my DLL will not load the settings on subsequent runs of the host application. The supportedRuntime of the application.exe.config has an impact on this - changing or deleting it will mean that the user.config file is saved with a different Version=X.X.X.X in it. With Version=2.0.0.0 my settings load just fine.

How can I get my settings to load/save without a problem without updating the host application.exe.config file? Or do I need to consider using an alternative storage location for my application settings, such as my own XML config file or registry?

GreenCoder
  • 13
  • 1
  • 3
  • If you don't want to update the host app config, you can create a folder structure and provide an inner config file which will override the settings of the parent config... – sajoshi Mar 08 '11 at 05:33
  • Also checkout http://bytes.com/topic/net/answers/654327-app-config-probing – sajoshi Mar 08 '11 at 05:33
  • @sajoshi - that sounds interesting, could you provide more details or a link to further details? – GreenCoder Mar 08 '11 at 06:21

1 Answers1

1

There's something missing from this question. A DLL cannot have its own .config file, its configuration sections must be merged into the app.exe.config file. Sounds to me you don't control this file, how do you prevent the owner of the app from breaking you when he reinstalls or updates his .config file?

At any rate, the lack of control you have is very troublesome. Storing your own settings without using a .config file is strongly indicated. An .xml file will do just fine.

Hans Passant
  • 922,412
  • 146
  • 1,693
  • 2,536
  • You're right - my DLL config file is redundant. And the lack of of control concerns me. I will go down the road of storing my own settings. – GreenCoder Mar 08 '11 at 06:22
  • I'm not sure he understood the issue you were raising,but at least he got a good answer! – Ritch Melton Mar 08 '11 at 06:29