Part 1 - The Problem Part 2 - Take this for example... Part 3 - Time for some code Part 4 - Why doesn't this work? Part 5 - The Remedy Part 6 - Putting it to work   Putting it to work   So, using this code, you could embed in your Feature receiver a web.config file that looks like the aforementioned fragment.  Read in ...

Part 1 - The ProblemPart 2 - Take this for example...Part 3 - Time for some codePart 4 - Why doesn't this work?Part 5 - The RemedyPart 6 - Putting it to work The Remedy  Ok, so now the Name property is only an XPath expression if it’s a child node.  Then what do we do with sections that have attributes?  They must be child nodes, and so created ...

Part 1 - The Problem Part 2 - Take this for example... Part 3 - Time for some code Part 4 - Why doesn't this work? Part 5 - The Remedy Part 6 - Putting it to work   Why doesn't this work?   My code would step through this XML, and at each node generate a new SPWebConfigModification.  The <location ...

Part 1 - The Problem Part 2 - Take this for example... Part 3 - Time for some code Part 4 - Why doesn't this work? Part 5 - The Remedy Part 6 - Putting it to work   Time for some code   I wrote some recursive code to load an xml document and from that document generate SPWebConfigModification objects.  Basically, you ...

Part 1 - The Problem Part 2 - Take this for example... Part 3 - Time for some code Part 4 - Why doesn't this work? Part 5 - The Remedy Part 6 - Putting it to work   Take this for example...   You write a feature to be installed and you make web.config modifications that include adding a section.  Later, that feature ...