• A Separate Configuration Section
  To do this implement a custom constructor or call the constructor with a parameter of false.
  

  public WebStoreConfig() 
  {
     this.SetConfigurationSection("wwWebStore"); 
     this.ReadKeysFromConfig();
  }

• A Separate Configuration File
  This will store the configuration settings in a file completely separate from the standard application .Config file. It will have the same structure as a configuration file. To do this implement a custom constructor or call the constructor with false and call the ReadKeysFromConfig() method with a filename.

  public WebStoreConfig() 
  {
     // *** Use a custom Config file
     this.ReadKeysFromConfig(@"d:\projects\wwWebStore\MyConfig.config");
  }

  
  This is especially useful for WinForms apps so your config settings don't get hammered by App.Config everytime you run your project. Note that you can also

  Note: If you manually read or write settings in your code make sure you always pass the filename to ReadKeysFromConfig() and WriteKeysFromConfig()!
  

Note you don't have to implement constructors as I do here. You can simple call the Constructor with false to stop the app from reading the settings from the default location.

For example you can simply do this to instantiate your class:

WebStoreConfig Configuration = new WebStoreConfig();
Configuration.SetEnryption("ConnectionString,MailPassword","EncryptThis");
Configuration.SetConfigurationSection("wwWebStore");
Configuration.ReadKeysFromConfig("wwWebStore.Config");

I simply prefer having a constructor that takes care of this for me so that I don't have to remember what I need to do to get the object instantiated.