This documentation is archived and is not being maintained.

Configuring the Script Task in the Script Task Editor

Before you write custom code in the Script task, you configure its principal properties in the three pages of the Script Task Editor. You can configure additional task properties that are not unique to the Script task by using the Properties window.

On the General page of the Script Task Editor, you assign a unique name and a description for the Script task.

The Script page of the Script Task Editor displays the custom properties of the Script task.

ScriptLanguage Property

Microsoft Visual Basic .NET is the only programming language supported by Visual Studio for Applications (VSA) at the present time. Therefore you cannot change this value.

PrecompileScriptIntoBinaryCode Property

You can specify that the code you write in the Script task is precompiled, instead of being compiled just-in-time at run time. By default, the value of this Boolean property is True. While precompiling the code provides a performance gain for the Script task, the embedded binary code also significantly increases the size of the saved package.

Scripts must be precompiled to be used on 64-bit computers. For more information, see Integration Services Considerations on 64-bit Computers.

After you change the value of the PrecompileScriptIntoBinaryCode property from False to True, you must reopen the script in the VSA IDE at least once to permit the Visual Studio tools to compile the code.

EntryPoint Property

The EntryPoint property specifies the class in the VSA project that the Integration Services runtime calls as the entry point into the Script task code. By default, the value of this string property is ScriptMain, and the Script task creates a class by the same name when it is opened for the first time in a new Script task. If you change the name of the class in the VSA project, or if you want the Script task to launch a different class in the project, you must change the value of the EntryPoint property.

ReadOnlyVariables and ReadWriteVariables Properties

You can enter comma-delimited lists of existing variables (without spaces) as the values of these properties to make the variables available for read-only or read/write access within the Script task code. Variables of both types are accessed in code through the Variables property of the Dts object. For more information, see Using Variables in the Script Task.

Variable names are case-sensitive.

Design Script Button

The Design Script button launches the VSA development environment in which you write your custom script. For more information, see Coding and Debugging the Script Task.

On the Expressions page of the Script Task Editor, you can use expressions to provide values for the properties of the Script task listed above and for many other task properties. For more information, see Using Expressions in Packages.