I have a solution that needs modifications to web.config to work (Enterprise Library Logging Application Block and a WCF Client configuration). The solution is scoped to a site collection.
I have found two possible methods for doing this with feature installation / activation - creating a supplemental web.config or using SPWebConfigModification in a feature receiver. Of these options, the supplemental web.config will be added to all web applications, not just the one/s that the feature is installed / activated on. Using SPWebConfigModification has led to being able to add entries but not remove them (discussed on SharePoint Overflow - http://sharepoint.stackexchange.com/questions/60468/web-config-entries-not-being-removed-during-feature-deactivation). So far, I'm left with either of these options as is, or making manual modifications each time I deploy the feature to a sith collection within a new web application (not desirable). So, what techniques are people using to modify web.config, what problems have occurred for them and how are they being fixed? Cheers Mike
_______________________________________________ ozmoss mailing list [email protected] http://prdlxvm0001.codify.net/mailman/listinfo/ozmoss
