Create a Custom Task
In the previous chapters, you created some very useful Script Tasks to help you with all kinds of tasks. The downside of using a Script Task is that the code is stored in the package itself. If you have multiple packages using the same Script Task, then you end up with a whole bunch of Script Tasks—each using its own copy of the code. When you need to fix a bug or add some extra functionality, you first have to find all the packages that use that particular Script Task and then change them all, one by one.
Another problem with the Script Task is that it requires some .NET knowledge. No problem for you, but most ...