views:

1890

answers:

4

I'd like to store a simple key/value string dictionary in my web config file. Visual Studio makes it easy to store a string collection(see sample below) but I'm not sure how to do it with a dictionary collection.

        <ArrayOfString xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema"&gt;
          <string>value1</string>
          <string>value2</string>
          <string>value2</string>
        </ArrayOfString>
+2  A: 

You would need to implement a custom section (See Configuration Section Designer).

What you really want... is something close to this:

<MyDictionary>
  <add name="Something1" value="something else"/>
  <add name="Something2" value="something else"/>
  <add name="Something3" value="something else"/>
</MyDictionary>

Where the XmlAttribute "name" is a Key which it won't allow to have more than one in the code behind. At the same time, make sure that the Collection MyDictionary is also a Dictionary.

You can do all of this with this tool and fill the gap as needed.

Maxim
Cant you use the Key-attribute instead of Name? <add key="UserName" value="Stefan"/> I know I have a couple of those in the appsettings-section for some variables I use in the website.
Stefan
A: 

I'm not sure how to store a Dictionary directly but you could easily use an array of strings to store a dictionary. For every key, value pair you save out the key as the first string and the value as the second. Then when rebuilding the dictionary you can undo this encoding.

static Dictionary<string,string> ArrayToDictionary(string[] data) {
  var map = new Dictionary<string,string>();
  for ( var i=  0; i < data.Length; i+=2 ) {
    map.Add(data[i], data[i+1]);
  }
  return map;
}
JaredPar
+10  A: 

Why reinvent the wheel? The AppSettings section is designed for exactly the purpose of storing dictionary-like data in your config file.

If you don't want to put too much data in your AppSettings section, you can group your related values into their own section as follows:

<configuration>
  <configSections>
    <section 
      name="MyDictionary" 
      type="System.Configuration.NameValueFileSectionHandler,System, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
  </configSections>

  <MyDictionary>
     <add key="name1" value="value1" />
     <add key="name2" value="value2" />
     <add key="name3" value="value3" />
     <add key="name4" value="value4" />
  </MyDictionary>
</configuration>

You can access elements in this collection using

using System.Collections.Specialized;
using System.Configuration;

public string GetName1()
{
    NameValueCollection section =
        (NameValueCollection)ConfigurationManager.Sections["MyDictionary"];
    return section["name1"];
}
Juliet
This is what I needed. Now, being a VB programmer I'd like to get it into the MySettings part of the web.config!
TGnat
@TGnat, do you have my.settings in webprojects? I dont. In winform-projects the app.config and my.settings are syncroniced against each other I think.
Stefan
Yes, The code sample I included in the question was copied from a My.Setting in the web.config.
TGnat
I tried to use the above code in my project, but ran into a problem when I included it after my <appSettings> element. Moving the custom stuff above appSettings seemed to fix it (not sure why). Also, I was able to drop the full type name and just use type="System.Configuration.NameValueFileSectionHandler".
Nogwater
+1  A: 

Juliet's answer is on point, but FYI you can also put additional configs in external .config files, by setting up your web.config as follows:

<?xml version="1.0"?>
<configuration>
  <configSections>
    <!-- blah blah the default stuff here -->

    <!-- here, add your custom section -->
    <section name="DocTabMap" type="System.Configuration.NameValueFileSectionHandler, System, Version=1.0.3300.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" />
  </configSections>

  <!-- your custom section, but referenced in another file -->
  <DocTabMap file="CustomDocTabs.config" />

  <!-- etc, remainder of default web.config is here -->
</configuration>

Then, your CustomDocTabs.config looks like this:

<?xml version="1.0"?>
<DocTabMap>
  <add key="A" value="1" />
  <add key="B" value="2" />
  <add key="C" value="3" />
  <add key="D" value="4" />
</DocTabMap>

Now you can access it in code via:

NameValueCollection DocTabMap = ConfigurationManager.GetSection("DocTabMap") as NameValueCollection;
DocTabMap["A"] // == "B"
Factor Mystic