I used this approach to create a template for all packages, and while I am really chuffed with the capabilities I am getting an error when I copy the template to a new package.
The last step in the logging process is to reset the variables, which uses the script component. When I copy the package, this new package cannot find the scripts, until I open the components inside the event handler, open the script in the editor and save it again. The step fails, resulting in the values being stuck at their last value until another step uses them.
I cannot put this template to production with this flaw in it, as ETL people will undoubtly forget to follow the above described procedure for a couple of packages they create.
Any ideas how to solve this? Does SSIS store the script in a pre-parsed location with an unique ID? Should I put the script in a variable from which all components read at runtime?