Jeff Rosenberg

@jmezach @ErikEJ I think this is a relatively-common problem for users -- at least, we've heard about this issue several times, including from myself with #51. It would be technically...

> I also think that a reference would be the best and we would also avoid the roundtrip. And the way beyond that already exists in classic Sql projects. @BenjaminAbt...

@jmezach I think that solution would be fine; the one reason I might prefer publishing a `master.dacpac` NuGet package would be to keep the syntax for database references consistent, rather...

Yes, that looks like what I have. I agree with confirming that the reference has been added. @BenjaminAbt one thing you may need to do -- it's unclear from the...

Yeah, looks like the package reference isn't being resolved properly. Here's what my `master.nupkg` looks like in my local NuGet repo, does yours look the same (other than names and...

@jmezach on the first question, I can see your point, but I see it a little differently -- you always get access to the API provided by the master database,...

> For a given version of SQL Server, does every instance of SQL Server have the exact same `master` database? Yes, the `master`, `model`, and `msdb` databases are shipped along...

Fair warning here: while we provide the publish feature as a convenience for development, it's not the primary focus of this project, and most of our efforts go towards our...

Sorry for the double post everyone, I commented the first time using the wrong Github account, I've removed the original comment and re-posted from the correct account. 😰

If sqlpackage doesn't support it either, then it's probably significantly more challenging than I thought and almost certainly outside our scope 🙂