Had a little trouble getting a COM (interop) dll/tbl from working in a SSIS's script task, while a similar program in a normal C# project would run sucessfully.
First thing I did was a quick registry hack to turn logging on for interop:
HKEY_LOCAL_MACHINE/SOFTWARE/MICROSOFT/Fusion
and created a new DWORD called EnableLog
and set the value to 1
This then gave me more info when I ran the package "without debugging".
In this case, it was having trouble finding my interop dll, because it was looking in the SQL-Server and .Net directories instead of the build directory.
So, as a quick solution, I copied the interop dlls from the build directory and drop them in the necessary folders:
C:\Program Files\Microsoft SQL Server\100\DTS\Binn\
-and-
C:\Windows\Microsoft.NET\Framework\v2.0.50727
First thing I did was a quick registry hack to turn logging on for interop:
HKEY_LOCAL_MACHINE/SOFTWARE/MICROSOFT/Fusion
and created a new DWORD called EnableLog
and set the value to 1
This then gave me more info when I ran the package "without debugging".
In this case, it was having trouble finding my interop dll, because it was looking in the SQL-Server and .Net directories instead of the build directory.
So, as a quick solution, I copied the interop dlls from the build directory and drop them in the necessary folders:
C:\Program Files\Microsoft SQL Server\100\DTS\Binn\
-and-
C:\Windows\Microsoft.NET\Framework\v2.0.50727
