Geeks With Blogs

The Life and Times of a Dev Yes, we're really that weird

I'm trying to use ApplicationSettings in the following scenario:

The settings are not all completely defined at design time (think plug-ins, but not completely that) and can be added by clients over time.

I can't find a way to make AppplicationSettings recognize new settings that weren't part of what it was compiled against.

I would have thought that this would be something pretty basic that they would add.

For example:

<TestAppSettings.TestSettings>
   
<setting name="DefaultSetting" serializeAs="String">
      <
value>Default Setting Value</value>
   </setting>
</TestAppSettings.TestSettings>

Then, after we ship, they need to add another setting:

 <TestAppSettings.TestSettings>
   
<setting name="DefaultSetting" serializeAs="String">
      <
value>Default Setting Value</value>
   </setting>
   <setting name="AnotherSetting" serializeAs="String">
      <
value>Another Setting Value</value>
   </setting>
</TestAppSettings.TestSettings>

I can't seem to get the code or the settings file to recognize AnotherSetting without modifying the wrapper class and adding AnotherSetting as a property.  When I iterate over the propertyvalues or the properties collection, the new setting doesn't show up, which I would have expected it to do.

Any ideas or suggestions?

Posted on Friday, January 5, 2007 6:06 PM Work | Back to top


Comments on this post: Am I missing something (ApplicationSettings)?

No comments posted yet.
Your comment:
 (will show your gravatar)


Copyright © Robert May | Powered by: GeeksWithBlogs.net