BEN ABT

Thanks for your improvement. Any public branch I could review the code?

I agree with you that the proposal is far from the perfect solution. The perfect solution would be not to need an external package for master schemas, but for example...

Just so I understand it better myself: why is it a bad practice? From my perspective, it is currently that I have to unnecessarily setup a package management that was...

> The whole conversation is really frustrating to me, since NuGet is clearly the correct solution here [..] and that it's even available in open-source repos such as Azure Data...

Hi, thanks for all of your feedback! I have seen the functionality with NuGet packages, but I was not aware that this was also used or intended for system databases....

How must the master database NuGet look like and/or be structured? I put the master.dacpac as content into a NuGet pkg, put the pkg in local folder of the solution,...

The nuspec file: ```xml MyProject.Database.MasterAzureSQLV12 1.0.0 MyProject false MSSQL Master Table Azure V12 ``` cspoj ```xml netstandard2.0 SqlAzure ``` Solution show everything should be recognized:  but errors like >...

The package is located to a local solution folder named "packages" . The local folder is added as source in the NuGet config ```xml ``` this is the recommended way...

Yes, the way to rename to master works. Thank you!! > 2>Adding reference to C:\Users\Ben\.nuget\packages\master\1.0.0/tools/master.dacpac with external parts master To name the dacpac to 'MyProject.Database.MasterAzureSQLV12' does not work.

I created a demo project to show you my errors but in this case it works.   I will check what are the differences why to use another name...