CODEWITHSUNDEEP
sql-serversql-server-2012tfsbuilddacpacdata-tier-applications
Nirman
Nirman

Reputation: 6793

dacpac - CLR assembly reference path issue

Following is the exact scenario in my database project, where I am creating dacpac to deploy databases on target SQL instance:

– when i try to run sqlpackage.exe to deploy the dacpac (generated in TFS build process) in my environment, I get an error saying –

*** No file was supplied for reference XXXX.XXXX.XXXX.dll; deployment might fail. When C:\Temp\Dacpac_testing\XXX.XXXXX.XXXX.dacpac was created, the original referenced file was located C:\BUILDS\1\XXXX\XXXX\SRC\XXXXXXXX\ASSEMBLIES\XXXX.XXXX.XXXX.dll

How can I create a dacpac to reference the path of CLR assembly on deployment environment (and not the one that was used at the time of building dacpac)

Any help on this will be much appreciated.

Upvotes: 2

Views: 2426

Answers (2)

Kevin
Kevin

Reputation: 463

I was able to solve this issue by including all the files in the bin/output folder that is built by the SSDT project on the machine that is deploying the dacpac. This folder includes all the referenced DLLs and DAPACs. I also included the publish.xml file and some sample SQLPackage cmd files in the build output to make it easy to deploy.

I found the answer from a post by Richard Gavel in the SQL Server Data Tools forum. https://social.msdn.microsoft.com/Forums/sqlserver/en-US/aba60b70-396f-4624-890c-015c1f2d68f7/dacpac-dependencies-for-sqlpackageexe?forum=ssdt

I don't know if this helps but I was having trouble running SqlPackage /Action:Script between my compiled DACPAC and an extracted DACPAC and got a similar error (An error occurred while adding references). I resolved it by copying all the DACPACS from the \bin\debug directory of my DACPAC (it has about references to 15 other database projects plus master and msdb). After that, it worked. So it seems that in looking for references, it will check the directory first (I don't know if it was looking specifically at the current directory or the one the root DACPAC was in because those were one and the same).

Upvotes: 2

Louis Lewis
Louis Lewis

Reputation: 1308

Sorry I only picked on this thread now, but I had a similar issue. Open the references in the Sql Server project, go to the dll that you are referencing right click and select properties.

Change the following settings: Generate Sql Script: True Model Aware: True

Select the relevant Permission set as required by the clr code.

Upvotes: 1

Related Questions