Hi jtseltmann,
By default, SQL Server Integration Services(SSIS) saves the references in a package definition. When we view code of a package that includes a script task, we will get the following section:
<ItemGroup>
<Reference Include="Microsoft.SQLServer.DTSRuntimeWrap, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91, processorArchitecture=x86" />
<Reference Include="System" />
<Reference Include="System.AddIn, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=MSIL" />
<Reference Include="System.Data" />
<Reference Include="System.Windows.Forms" />
<Reference Include="System.Xml" />
<Reference Include="Microsoft.SqlServer.ManagedDTS, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" />
<Reference Include="Microsoft.SqlServer.ScriptTask, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" />
</ItemGroup>
In this case, please build the script task(in code design mode, right-click the code project, and then click build), close the code designer, save the package, and then reopen the package to check if the reference is still there.
Or, please view the code of the package, and add to following line to the ItemGroup element manually to fix the issue:
<Reference Include="Microsoft.SQLServer.DTSRuntimeWrap, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91, processorArchitecture=x86" />
If you have any more questions, please feel free to ask.
Thanks,
Jin ChenJin Chen - MSFT
There is an amazing pack of free network admin tools.
click here to download it