referencing-other-assemblies-in-scripting-solutions.md

title	Referencing Other Assemblies in Scripting Solutions | Microsoft Docs
ms.custom
ms.date	03/06/2017
ms.prod	sql-server-2014
ms.reviewer
ms.technology	integration-services
ms.topic	reference
dev_langs	VB
helpviewer_keywords	SSIS Script task, .NET Framework Script task [Integration Services], adding references referencing custom assemblies SSIS Script task, VisualBasic namespace assemblies [Integration Services] VisualBasic namespace Script task [Integration Services], VisualBasic namespace Microsoft.VisualBasic namespace Script task [Integration Services], .NET Framework .NET Framework [Integration Services] referencing Web services
ms.assetid	9b655bcd-19f6-43d8-9f89-1b4d299c6380
author	janinezhang
ms.author	janinez
manager	craigg

Referencing Other Assemblies in Scripting Solutions

The [!INCLUDEmsCoName] [!INCLUDEdnprdnshort] class library provides the script developer with a powerful set of tools for implementing custom functionality in [!INCLUDEssISnoversion] packages. The Script task and the Script component can also use custom managed assemblies.

Note

To enable your packages to use the objects and methods from a Web service, use the Add Web Reference command available in [!INCLUDEmsCoName][!INCLUDEvsprvs] Tools for Applications (VSTA). In earlier versions of [!INCLUDEssISnoversion], you had to generate a proxy class to use a Web service.

Using a Managed Assembly

For [!INCLUDEssISnoversion] to find a managed assembly at design time, you must do the following steps:

1. Store the managed assembly in any folder on your computer.

   [!NOTE] In earlier versions of [!INCLUDEssISnoversion], you could only add a reference to a managed assembly that was stored in the %windir%\Microsoft.NET\Framework\vx.x.xxxxx folder or the %ProgramFiles%\Microsoft SQL Server\100\SDK\Assemblies folder.

2. Add a reference to the managed assembly.

   To add the reference, in VSTA, in the Add Reference dialog box, on the Browse tab, locate and add the managed assembly.

For [!INCLUDEssISnoversion] to find the managed assembly at run time, you must do the following steps:

1. Sign the managed assembly with a strong name.

2. Install the assembly in the global assembly cache on the computer on which the package is run.

   For more information, see Building, Deploying, and Debugging Custom Objects.

Using the Microsoft .NET Framework Class Library

The Script task and the Script component can take advantage of all the other objects and functionality exposed by the [!INCLUDEdnprdnshort] class library. For example, by using the [!INCLUDEdnprdnshort], you can retrieve information about your environment and interact with the computer that is running the package.

This list describes several of the more frequently used [!INCLUDEdnprdnshort] classes:

• System.Data Contains the ADO.NET architecture.

• System.IO Provides an interface to the file system and streams.

• System.Windows.Forms Provides form creation.

• System.Text.RegularExpressions Provides classes for working with regular expressions.

• System.Environment Returns information about the local computer, the current user, and computer and user settings.

• System.Net Provides network communications.

• System.DirectoryServices Exposes Active Directory.

• System.Drawing Provides extensive image manipulation libraries.

• System.Threading Enables multithreaded programming.

For more information about the [!INCLUDEdnprdnshort], see the MSDN Library.

Stay Up to Date with Integration Services
For the latest downloads, articles, samples, and videos from Microsoft, as well as selected solutions from the community, visit the [!INCLUDEssISnoversion] page on MSDN:

Visit the Integration Services page on MSDN

For automatic notification of these updates, subscribe to the RSS feeds available on the page.

See Also

Extending Packages with Scripting