Visual Studio 2017 SSDT adds hardcoded master.dacpac include
Visual Studio 2017 seems to add a hardcoded path to the master.dacpac if I include it in a project of mine. Older versions of the SSDT used the $(DacPacRootPath) variable to get the master.dacpac.
This is really annoying as it breaks the builds on our build server where the master.dacpac is installed in a different folder than on my development machine.
This issue was recently fixed in our internal branch. The fix will be included in the next major version of Visual Studio (i.e. 2019)
Jonathan N commented
Seems like the fix has also been released to Visual Studio 2017 version 15.9.13.
Martin Z commented
So you're telling me you're going to go an entire 2-year product release cycle with SSDT support in MSBuild totally broken.
Needs fixing in VS2017 update as well, not only VS2019
This is crazy. Please fix so we can have dynamic paths to reference databases again.
Can we get an update on when this will be fixed?
My Ka commented
still have it in VS2017 15.9.2
Joshua Darnell commented
Just ran into this today. The workaround is not terrible, but it would be great to see the regression fixed to avoid the troubleshooting / etc.
Jason Kohlhoff commented
Any news on when the update will be released? This breaks our automated builds whenever we change master.dacpac references. We also have a mix of developers running Professional and Enterprise editions, so local builds fail.
Is there an estimate when this will be fixed? It is so easy to run into this problem and it is frustrating to have to fix this manually each time. Especially considering this used to work fine in older versions.
Felix M commented
For discussion and solution of this bug have a look at https://stackoverflow.com/questions/45103775/hosted-vs2017-agent-build-master-dacpac-does-not-exist?rq=1 .
Brian Lawton commented
Here's a link to my original post...
Brian Lawton commented
Just a note that this issue still exists today when using the combination VS 2017 15.5.6 Enterprise with SSDT 15.5.2. A colleague opening the project I recently created us same tool versions except Professional edition encountered the hardcoded path. Once we change it to the expected relative path, the master reference worked as expected. I reported this error previously via the old Connect site when the SSDT for VS2017 was still in beta but it has not yet been addressed.