tag:help.appveyor.com,2012-11-13:/discussions/questions/4274-ssdt-projects-with-external-dependenciesAppVeyor: Discussion 2018-08-25T02:17:45Ztag:help.appveyor.com,2012-11-13:Comment/426801782017-06-02T22:52:35Z2017-06-02T22:52:35ZSSDT projects with external dependencies<div><p>Hi Andrew,</p>
<p>We don't have this functionality out of the box, but I believe the following workaround might work:</p>
<ul>
<li>
<p>in <code>database.dacpac</code> you set absolute path to the <code>master.dacpac</code> dependency, not relative to <code>database.dacpac</code> location. Look at <a href="https://social.msdn.microsoft.com/Forums/sqlserver/en-US/8ad14c4c-fb37-4ab3-b5c1-aafac11886dd/dacpac-location-database-reference?forum=ssdt">this</a> thread - you can use environment variable to switch this path between build and local machines.</p>
</li>
<li>
<p><a href="https://www.appveyor.com/docs/api/samples/download-artifacts-ps/">Download</a> <code>master.dacpac</code> to that absolute path in <a href="https://www.appveyor.com/docs/deployment/agent/#running-powershell-scripts-on-target-server-during-deployment">before-deploy.ps1</a>.</p>
</li>
</ul>
<p>Let us know if this works for you.</p>
<p>Ilya.</p></div>Ilya Finkelshteyntag:help.appveyor.com,2012-11-13:Comment/426801782017-06-05T16:06:57Z2017-06-05T16:06:57ZSSDT projects with external dependencies<div><p>Hi,</p>
<p>I got it working in the end by zipping up the dacpacs, adding a deploy.ps1 to call SQLPackage.exe and deploying it in AppVeyor using the application settings and environment variables for connection string etc.</p>
<p>Andrew.</p></div>andrewtag:help.appveyor.com,2012-11-13:Comment/426801782017-06-05T16:09:03Z2017-06-05T16:09:03ZSSDT projects with external dependencies<div><p>Good, thank you for update!</p></div>Ilya Finkelshteyn