June 10, 2015 at 3:52 pm
If I have a database reference to say, master or any other DB dacpac for that matter, in my Db project. When I branch my project in TFS the database reference in the branched version becomes invalid and I have to remove the reference and re-insert it to make it valid again. Is there anyway I can avoid having to redo this every time I branch
June 11, 2015 at 2:07 am
Are the referenced items part of the branch?
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
June 11, 2015 at 2:27 pm
Phil, not sure I understand the question. When I branch and then open the branched solution the reference are there, however they are invalid. It's almost like these reference are just pointers to dacpacs
June 12, 2015 at 5:20 am
Paul Sims-405749 (6/11/2015)
Phil, not sure I understand the question. When I branch and then open the branched solution the reference are there, however they are invalid. It's almost like these reference are just pointers to dacpacs
The references are pointers to dacpacs.
Open up your .sqlproj file and you'll find an 'ArtifactReference' group for each referenced database.
For example:
<ArtifactReference Include="$(DacPacRootPath)\Extensions\Microsoft\SQLDB\Extensions\SqlServer\110\SqlSchemas\master.dacpac">
<HintPath>$(DacPacRootPath)\Extensions\Microsoft\SQLDB\Extensions\SqlServer\110\SqlSchemas\master.dacpac</HintPath>
<SuppressMissingDependenciesErrors>False</SuppressMissingDependenciesErrors>
<DatabaseVariableLiteralValue>master</DatabaseVariableLiteralValue>
</ArtifactReference>
I have no idea where 'DacPacRootPath' comes from, however.
The absence of evidence is not evidence of absence
- Martin Rees
The absence of consumable DDL, sample data and desired results is, however, evidence of the absence of my response
- Phil Parkin
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply