I think you can't do that from DNN manifest. CMIIW.

You should do from .NET code. Maybe from Page_Load or something.

CMIIW.

A better place would have been to implement IUpgradable & perform config changes there. Config changes are one time changes, and doing them in Page_Load would recursively (and infinitely) lead to AppDomain recycling as each request to that page would again modify web.config, not to mention the preformance hit of parsing xml each time page is requested, even if you check for changes before performing them again.

Thanx, that was what I was looking for. However, I would suggest DNN team to add an option that allows the change to be updated (if it exists) or added if it does not exist.So, does the "update" action actually checks for node existence, updating if it exists or adding it if NOT?? or it simply tries to update it??