December 24, 2009
When building an application for SharePoint, if you’re making changes to the Web.config, they should be deployed SPWebconfigModifications. This isn’t that easy, really, but works well enough, and there are good articles about how to add them – but my code looks like:
SPWebConfigModification modification = new SPWebConfigModification(
"add[@name='MyNavProvider']",
"configuration/system.web/siteMap/providers");
modification.Value = "<add name=\"MyNavProvider\" type=\"{Assembly info here!}\" />";;
modification.Sequence = 0;
modification.Type = SPWebConfigModification.SPWebConfigModificationType.EnsureChildNode;
modification.Owner = "MyConfigModification;
webApp.WebConfigModifications.Add(modification);
webApp.Update();
That works, but what about removing them? It’s important to do this – otherwise you can cripple a system. Read more »
