A blog about SQL Server, SSIS, C# and whatever else I happen to be dealing with in my professional life.

Find ramblings

Friday, October 5, 2012

EzAPI 2012 referenced assembly issue

A brief post on using the current source build of EzAPI. If you try to compile it, you will receive this error

Assembly 'Microsoft.SqlServer.TxScript, Version=, Culture=neutral, PublicKeyToken=89845dcd8080cc91' uses 'Microsoft.SqlServer.VSTAScriptingLib, Version=, Culture=neutral, PublicKeyToken=89845dcd8080cc91' which has a higher version than referenced assembly 'Microsoft.SqlServer.VSTAScriptingLib, Version=, Culture=neutral, PublicKeyToken=89845dcd8080cc91'

No problem you say. You expand your references and see that the project found the 2008 DLL and you just need to change the path from "C:\Program Files (x86)\Microsoft SQL Server\100\SDK\Assemblies\Microsoft.SqlServer.VSTAScriptingLib.dll" to "C:\Program Files (x86)\Microsoft SQL Server\110\SDK\Assemblies\Microsoft.SqlServer.VSTAScriptingLib.dll"

The only problem is, there isn't a "c:\Program Files\Microsoft SQL Server\110\DTS\PipelineComponents\Microsoft.SqlServer.TxScript.dll"

I have no idea why that DLL isn't installed in that location, or any location in the Program Files|Program Files (x86) location but whatever. The assembly is on the machine as SSIS works, you'll simply need to get it out of the GAC (Global Assembly Cache). I'm lazy and just repointed my reference into the GAC but the other option is to copy it into the expected location.

copy C:\Windows\Microsoft.NET\assembly\GAC_MSIL\Microsoft.SqlServer.VSTAScriptingLib\v4.0_11.0.0.0__89845dcd8080cc91\Microsoft.SqlServer.VSTAScriptingLib.dll "c:\Program Files (x86)\Microsoft SQL Server\110\DTS\PipelineComponents"

No comments: