4

I'm trying to create classes to read from my config file using ConfigurationSection and ConfigurationElementCollection but am having a hard time.

As an example of the config:


<PaymentMethodSettings>
  <PaymentMethods>
    <PaymentMethod name="blah blah" code="1"/>
    <PaymentMethod name="blah blah" code="42"/>
    <PaymentMethod name="blah blah" code="43"/>
    <Paymentmethod name="Base blah">
      <SubPaymentMethod name="blah blah" code="18"/>
      <SubPaymentMethod name="blah blah" code="28"/>
      <SubPaymentMethod name="blah blah" code="38"/>
    </Paymentmethod>
  </PaymentMethods>
</PaymentMethodSettings>
Little Larry Sellers
  • 270
  • 2
  • 5
  • 11
  • Can you give me a hint at what you want to do? I mean me offering an XMLReader seems fairly insulting when I don't know the reason behind it – websch01ar Oct 31 '08 at 21:15
  • He wants to use the built in Configuration classes with .NET, not parse the file manually. – FlySwat Oct 31 '08 at 21:30

2 Answers2

5

The magic here is to use ConfigurationSection classes.

These classes just need to contain properties that match 1:1 with your configuration schema. You use attributes to let .NET know which properties match which elements.

So, you could create PaymentMethod and have it inherit from ConfigurationSection

And you would create SubPaymentMethod and have it inherit from ConfigurationElement.

PaymentMethod would have a ConfigurationElementCollection of SubPaymentMethods in it as a property, that is how you wire up the complex types together.

You don't need to write your own XML parsing code.

public class PaymentSection : ConfigurationSection
{
   // Simple One
   [ConfigurationProperty("name")]]
   public String name
   {
      get { return this["name"]; }
      set { this["name"] = value; }
   }

}

etc...

See here for how to create the ConfigurationElementCollections so you can have nested types:

http://blogs.neudesic.com/blogs/jason_jung/archive/2006/08/08/208.aspx

FlySwat
  • 172,459
  • 74
  • 246
  • 311
3

This should help you figure out how to create configuration sections correctly, and then read from them.

DOK
  • 32,337
  • 7
  • 60
  • 92