0

I have created a .Net library to be used for SSIS Projects. We have created number of SSIS templates all using same dotnet library.

Can someone share - how can we ensure that if we make changes to our DLL and then it reflects to all SSIS templates which we have created.

Means storing DLL centrally which everyone can refer to.

Hadi
  • 36,233
  • 13
  • 65
  • 124
Conrad Jagger
  • 91
  • 1
  • 3
  • 11
  • 2
    You use assembly code, register it DAC, then it shouldn't matter where your dll is, projects will find it refering to the assembly. – YvesR Sep 27 '12 at 13:14
  • so registering in GAC will enable all application to use that. And if any changes to DLL is required, then again add DLL in GAC so that applications can access updated APP. – Conrad Jagger Sep 27 '12 at 13:18
  • That is the plan, yes :) – YvesR Sep 27 '12 at 13:50
  • The only thing you will need to do to your assembly is assign it a [strong name](http://support.microsoft.com/kb/302340) and *then* you can add it to the GAC via (gacutil -if MyAssembly.dll) where gacutil should be on your Visual Studio Command Prompt Path – billinkc Sep 27 '12 at 13:52
  • @ConradJagger To be clear, you are using a .Net library and not a custom component for SSIS? – J Weezy Mar 05 '19 at 16:58

1 Answers1

0

Ensure you strongly sign the DLL and deploy it to GAC. Then reference it in your SSIS templates.

Arthur
  • 1,441
  • 1
  • 13
  • 17