In a previous post, I wrote about using SSIS 2008 custom components in SSIS 2012. In that post, I noted that the custom component’s UI (Edit, Advanced Edit) does not work in SSDT.
It turns out there is a way to get some UI for some components to work though. The key is that the component’s assembly must be in the proper location for SQL Server 2012. The locations are listed below for reference. After copying the component’s assembly to it’s proper location, it will show up in the toolbox, which also enables the UI.
That will at least enable you to right-click on the component and see the Edit and Advanced Edit context menu entries. On one component, I am not able to pull up the custom UI because of what looks to be a different interface definition. The Advanced Editor (which is generic anyway) does work, thereby allowing me to edit all component settings even if it’s not as user friendly as using the component-specific UI.
I will sort things out some more, as it’s technically possibly that by adding additional assembly redirects, all UIs can be made to work. I’ve also noticed that after a package upgrade, the component’s icon is a generic one, but if you drag and drop a new instance of the component, its icon does show.
Extension Locations
For SQL Server 2012, the custom extension locations are listed below. Simply copy your extension’s assembly file to the proper folder depending on the type of extension.
Data Flow Pipeline Components:
C:\Program Files (x86)\Microsoft SQL Server\110\DTS\PipelineComponents
Foreach Enumerators:
C:\Program Files (x86)\Microsoft SQL Server\110\DTS\ForEachEnumerators
Control Flow Tasks:
C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Tasks
Sven Aelterman 