Hello,
It appears that deploying RadControlsSP.wsp now makes some changes to web.config automatically? Specifically I believe I am seeing an http handler automatically being registered. Can you confirm this?
Also, if this is true, is there any way to stop this from happening? We have deployments running the old version of this package, which did not automatically add the handler, so we created a powershell script that added it ourselves. But now when deploying the updated RadControlsSP.wsp package we are left with duplicate handler entries. A manual fix is possible, but do automated deployments to numerous environments, and manually fixing this issue on every web server in a SharePoint farm upon each deployment would be incredibly tedious.
Thank you,
Chris
It appears that deploying RadControlsSP.wsp now makes some changes to web.config automatically? Specifically I believe I am seeing an http handler automatically being registered. Can you confirm this?
Also, if this is true, is there any way to stop this from happening? We have deployments running the old version of this package, which did not automatically add the handler, so we created a powershell script that added it ourselves. But now when deploying the updated RadControlsSP.wsp package we are left with duplicate handler entries. A manual fix is possible, but do automated deployments to numerous environments, and manually fixing this issue on every web server in a SharePoint farm upon each deployment would be incredibly tedious.
Thank you,
Chris