The SSDT projects now seem to use dbmdl files instead but I don't see a way to I had no problem with unresolved references before I "upgraded" to SSDT, as the base project referenced the dbschema file of the add-on.
To indicate that the add-on is installed. There are triggers in the base database that have to push data to the add-on database, if a flag is set One is for a base product and the other is for an add-on option that some customers purchase and some do not. The projects belong is separate solutions. I made the same assumption as Bill - I assumed your two projects were in the same solution.
#Dbschema vs dacpac windows 8#
ObjectStorageHelper – A WinRT utility for Windows 8 | proj file that I use to build my database projects - all you need to do isĪlter it so that it builds multiple solutions rather than just one. This isn't as difficult as it sounds, below I have pasted the contents of a. Write an msbuild script that builds the solutions that contain the two projects in the required order.Move the two projects into the same solution.
I mmade the same assumption as Bill - I assumed your two projects were in the same solution. That might be true if the two projects were in the same solution, but they are not. The dialog that follows is very different to the project reference dialog, with a project dropdown that should already be populated with the second database project. You need to add a Database Reference between SQL Server Database projects, not a normal project reference.
0 kommentar(er)
