Ha! Never mind me. It turns out that the section name needs to match the namespace qualified name of the settings class and in this case it didn't. Not sure how that happened but adjusting it to match resulted in it working suddenly. Convention over fail FTW!
On Thu, Feb 9, 2012 at 9:42 AM, Michael Minutillo < michael.minuti...@gmail.com> wrote: > Hey folks, > > I have an Application scoped Application Setting called DataFile in my > Wolfbyte.Samples assembly. When I add a reference to this assembly from my > WCF project I should be able to override the value of DataFile at runtime > by putting the following in my web.config: > > <configuration> > <configSections> > <sectionGroup name="applicationSettings" > type="System.Configuration.ApplicationSettingsGroup, System, > Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" > > <section name="Wolfbyte.Samples.Properties.Settings" > type="System.Configuration.ClientSettingsSection, System, Version=2.0.0.0, > Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" > /> > </sectionGroup> > </configSections> > <applicationSettings> > <Wolfbyte.Samples.Properties.Settings> > <setting name="DataFile" serializeAs="String"> > <value>C:\New\Path\To\File</value> > </setting> > </Wolfbyte.Samples.Properties.Settings> > </applicationSettings> > </configuration> > > However it seems that this is not working and the value that is embedded > into the compiled assembly is being used. Has anyone ever run into this > issue and has some pointers of how I can debug this issue? This is an > existing application and I believe this was working previously. > > > Michael M. Minutillo > Indiscriminate Information Sponge > http://codermike.com >
