Web Config Modifications

Sep 7, 2010 at 3:23 AM
Edited Sep 7, 2010 at 3:26 AM

Is there any reason why the majority of the modifications to the web.config could not have been added as a feature receiver using the readily-available SPWebConfigModification class? I can appreciate that some of the others require user intervention.

Having to make thes changes to each web app manually is not only time-consuming but also introduces issues with tracking changes.

This small change would make this feature much more robust, while also allowing for the mods to be removed when the feature is deactivated or uninstalled.

Sep 8, 2010 at 4:30 PM

I completely agree with you - there are better ways to do most of the work in here.  What you are looking at is alpha code and code which was delivered in a very demanding timeframe.  I need to get back to this and update it, and the poor web.config experience is definitely a target.  However, time is tight and I am probably just not going to get to it.  I encourage you to update the code and post it back here for everyone else's benefit.