Calling external DLLs from a Script Task in SSIS 2. The 2. 01. 2 version of SQL Server has brought with it a number of new features, not least the new, Visual Studio 2. Management Studio. However, the changes are more than just aesthetic, as I found out when I came to try and upgrade some SQL Server Integration Studio SSIS packages from SQL server 2. Most packages upgraded fine, but there were some issues when I tried to upgrade any packages that used Script Tasks containing references to external DLLs. KB/DLL/585817/msiGAC.jpg' alt='Install Dll In Gac Without Gacutil Without Strong' title='Install Dll In Gac Without Gacutil Without Strong' />The Script Task is the most versatile component of SSIS. Triggers On Update Sql Server. Using either VB. NET or C code, you can basically do anything you want with it, from assigning variables, loadingwriting data, or even calling web services. The potential of the Script Task is virtually limitless, thanks to the ability to reference external DLLs. With SQL 2. 00. 8, referencing an external DLL was relatively simple, if a little convoluted. Youd create your external class library, making sure that youve signed the assembly with a strong named key file and set the correct target framework and CPU usually. NET 2 and relevant choice of x. Any CPU.  Youd then take this DLL, add it to the Global Assembly Cache GAC, and the DTS folder with your SQL install or alternatively the. NET Framework folder. Reference the assembly in your Script Task and youre there Links has the details of the pre SQL 2. I wont get into the details here. Wheres the GAC gone Now, as well as updating the shell and making SSIS 2. Script Tasks is that the default version of the. NET Framework has been updated to. NET 4.  One of the changes to. NET 4 was the addition of a brand new GAC, that sits alongside the previous one due to updates to the Common Language Runtime CLR. Install Dll In Gac Without Gacutil Without Strong' title='Install Dll In Gac Without Gacutil Without Strong' />Issue Today I went to install the Outlook plugin for Microsoft Identity Manager 2016 SP1 latest and greatest installed. To my surprise I was met with. Note that at time of writing, even with any Any CPU DLL and on a 64bit PC, I had to deploy the assembly into the Program Files x86Microsoft SQL Server. PDF files that contain the Visual Studio 2005 documentation. Today we welcome our guest blogger CRM MVP Darren Liu from the Crowe company. Many Microsoft Dynamics CRM MSCRM implementations involved integration with. Theres a good discussion of this over on Stackoverflow. It should be possible to change the Target Framework and Target CPU of your Script Task as with any Visual Studio project to match the version and CPU of your external DLL, however when I tried this, I ran into an unexpected bug. It seems that the editor in SSIS 2. UI, specifically with the Target Framework dropdown. While it changes the target framework as expected, this closes the project properties window and when you re open it, it will always show. NET 4 again.  This results in a situation where you can add. NET 2 DLLs to the project, but as soon as the package is executed, it throws a reflection error. Install Dll In Gac Without Gacutil Without Strong' title='Install Dll In Gac Without Gacutil Without Strong' />Please explain in detail the steps you did in both visual studio and in the console to install the program in to the GAC. Scott Chamberlain Aug 25 14 at 2113. Microsoft. Net Assembly is a logical unit of code, it contains code that the Common Language Runtime CLR executes. So, without manually editing the project XML file which is an option but remember theyre temporary, the easiest option seems to be to upgrade our external DLL to. NET 4 its better anyway, and deploy to the new folders. Deploy Deploy Deploy Once your external DLL has been rebuilt as a better, stronger, faster. NET 4 class library, and signed as with the previous version, you can deploy it to the new GAC, now located in C Windows. Microsoft. NETassembly. GACCPU versionIn addition, to run this locally, youll also need to add the DLL to the SQL Server assemblies folder, which has also moved slightly since 2. Its now in C Program Files x. Microsoft SQL Server. SDKAssemblies. Note that at time of writing, even with any Any CPU DLL and on a 6. PC, I had to deploy the assembly into the Program Files x. Microsoft SQL Server directory, not the Program Files. Microsoft SQL Server one. And that should be itFollow the same setup on your server and you shouldnt have any issues running your SSIS package. I had further problems installing to the GAC on the server due to not having GACUtil installed, so had to download the Windows 7. SDK to add my assemblies to the GAC. Has anyone had similar troubles getting custom assemblies to work in SSIS 2.