SSDT 2012可用的自定义转换任务在SSDT 2015中无法正常工作

Let's walk through the most probable causes and fixes for your custom transformation task working smoothly in SSDT 2012 but failing to function in SSDT 2015:

1. Framework & SSIS Runtime Version Mismatch #

SSDT 2012 is tied to SSIS 2012 and typically uses .NET Framework 4.0, while SSDT 2015 targets SSIS 2014/2016 and relies on .NET 4.5.2+. Your custom task might be built against incompatible versions:

• Check your custom task project's target .NET Framework. Rebuild it to target .NET 4.5.2 (match the framework SSDT 2015 uses).
• Verify the SSIS runtime assemblies you're referencing. Swap out older versions (like Microsoft.SqlServer.Dts.Runtime v11.0.0.0 for SSIS 2012) with the appropriate ones for SSIS 2014 (v12.0.0.0) or SSIS 2016 (v13.0.0.0), depending on your SSDT 2015 configuration.

2. GAC Deployment & Registry Registration Issues #

SSIS custom components require proper GAC deployment and registry registration to be detected by SSDT:

• Re-deploy your custom task to the Global Assembly Cache (GAC) using gacutil /i YourCustomTask.dll. Use the 64-bit gacutil if you're running a 64-bit SSDT 2015 instance.
• Validate the SSIS component registry entries for SSDT 2015. The correct paths are:
  • 32-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\VisualStudio\14.0\SSIS\DataFlowComponents
  • 64-bit: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\VisualStudio\14.0\SSIS\DataFlowComponents
    Ensure your component's GUID, name, and metadata are correctly registered here, matching the entries you set up for SSDT 2012.

3. Custom UI Editor Compatibility #

If your task includes a custom editor (the dialog that opens on double-click), VS 2015 Shell uses different extension APIs than VS 2012 Shell:

• Rebuild your UI editor project to reference VS 2015 SDK assemblies, like Microsoft.VisualStudio.Shell.14.0, instead of the VS 2012 equivalents.
• Use fuslogvw.exe (Assembly Binding Log Viewer) to track down any missing dependencies or assembly loading failures when trying to open the editor in SSDT 2015.

4. SSDT Project Target Configuration #

• Check your SSIS project's target server version in SSDT 2015: Go to Project Properties > Configuration Properties > General > TargetServerVersion. If your task was built for SSIS 2012, set this to SQL Server 2012 to avoid version mismatches.
• Install the latest updates for SSDT 2015. Microsoft released patches that fix component loading bugs, so updating might resolve the issue outright.

5. Debugging Loading Failures #

If the above steps don't work, dig deeper with debugging:

• Launch SSDT 2015 with debugging enabled from your custom task's source code project. Set breakpoints in Initialize or Validate methods to see if your component is even being initialized.
• Check the Windows Application Event Log for errors related to SSIS or your custom component. SSDT often logs assembly loading failures or initialization errors here.

内容的提问来源于stack exchange，提问作者Russ