Modifying the web.config with SPWebConfigModifications

A confusing aspect of using the SPWebConfigModifications is what should you use as the Name of your modification?

Here are my recommendations, I do not claim to have a complete or exact list, but this should help get you started.

  1. If you are adding items that will have repeating xml node names , like section or add, then your name should be something like the following to prevent overwriting any previously added modifications.
    1. add[@name=’name’] for <add name="name" …/>
    2. section[@name=’name’] for <section name="name" …/>
    3. etc.
  2. If you are adding custom xml nodes that will have child nodes then you should use the name of that node, this includes standard nodes located in the web.config file.
    1. membership for <membership>…</membership>
    2. etc.

If you need help, have haning web.config modifications etc, here is a link I found that provides a nice .aspx page that will allow you to remove those changes.  Also available at the link is more information about doing the web.config changes using SPWebConfigModification objects.

http://blog.thekid.me.uk/archive/2007/03/24/web-config-modification-manager-for-sharepoint.aspx

If you fail to name your modification properly then you might find that the next modification actually overwrites what you just added.


Another question I run across often is how to change the attribute of a tag that already exists.  It actually turns out that this is very simple.  Using the membership section of a web.config I will show you.

<system.web>
  <membership defaultProvider="AspNetActiveDirectoryMembershipProvider">
      <providers>
        <clear />
        <add name="AspNetActiveDirectoryMembershipProvider" type="…" connectionStringName="…" … />
      </providers>
  </membership>
</system.web>

Lets say we have our own membership provider and you plan on referencing it using the name "MyCustomMembershipProvider" your SPWebConfigModification would look like the following.  Rember you would have to also add a membership provider using a SPWebConfigModification and the naming described above.

SPWebConfigModification membershipProviderPrimary = new SPWebConfigModification("defaultProvider", "configuration/system.web/membership");
                membershipProviderPrimary.Type = SPWebConfigModification.SPWebConfigModificationType.EnsureAttribute;
                membershipProviderPrimary.Sequence = 0;
                membershipProviderPrimary.Owner = GetType().ToString();
                membershipProviderPrimary.Value = "MyCustomMembershipProvider";

Notice here set the name to the name of the xml attribute who’s value we want to set.  The XPath provided does not include the xml attribute, only the xml node which contains that attribute.  Finally, we set the SPWebConfigModification’s value to the desired value ("MyCustomMembershipProvider"). Once this change is commited you will see that the defaultProvider has been changed to "MyCustomMembershipProvider".

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s