Extending Packages with Scripting
If you find that the built-in components Integration Services do not meet your requirements, you can extend the power of Integration Services by coding your own extensions. You have two discrete options for extending your packages: you can write code within the powerful wrappers provided by the Script task and the Script component, or you can create custom Integration Services extensions from scratch by deriving from the base classes provided by the Integration Services object model.
This section explores the simpler of the two options — extending packages with scripting.
The Script task and the Script component let you extend both the control flow and the data flow of an Integration Services package with very little coding. Both objects use the Microsoft Visual Studio Tools for Applications (VSTA) development environment and the Microsoft Visual Basic 2008 or Microsoft Visual C# 2008 programming languages, and benefit from all the functionality offered by the Microsoft .NET Framework class library, as well as custom assemblies. The Script task and the Script component let the developer create custom functionality without having to write all the infrastructure code that is typically required when developing a custom task or custom data flow component.