RE: ConfigDefaultMain - what have you done?

["Addictive Software" <address@hidden>]

> Setting the ConfigDefaultMain dictionaries at design-time 
> works, but not at run-time.

This is not precisely correct.


The properties (ConfigDefaultXXX) all work when establishing a new user's
configuration (options).  Typically, when you see no reaction from changing
these to your application, its for one of two reasons:

1) You've not deleted the old configuration to try initializing it from the
default settings again (check the registry path, delete the key, and re-run
your application).

2) The configuration was loaded prior to your run-time code changing the
ConfigDefaultXXX properties.  This can be the case because a property access
or dictionary-related call has forced the configuration to be loaded, or
more typically, because a Live-Spelling control configured at design time
needed to load the configuration in order to paint spelling errors.  In this
case, the typical way around this is to change the ConfigKey (and thus force
the configuration to be reloaded) after changing the ConfigDefaultXXX
properties.


Best Wishes,

Michael Novak
Addictive Software
http://www.addictive-software.com/
address@hidden