Jonathan Mezach

@MHacker9404 I think you'll need to add `DatabaseVariableLiteralValue="master"` to the `PackageReference` element to mark it as an external database reference. Right now it assumes that the master objects are going...

@jeffrosenberg If I remember correctly you've done this, right? Any idea what's going on here?

That looks alright to me, but looking at the build output it somehow doesn't seem to include the reference to the `master.dacpac`. Could you try running `dotnet build .csproj -v...

I guess that you could create a separate `master.csproj` that would copy the `master.dacpac` to its output folder and then add a project reference to it and it would work....

@Belorus First of all, thank you for the encouragement, really means a lot! I believe what you are looking for is `SuppressTSqlWarnings`. This is described in more detail in our...

Thank you for your suggestions @sykesjd. I think this would be a great addition and I can see the value in it. If anyone is willing to implement this we...

@Vikenesh Based on the error message it looks like there's something wrong with the project file, since we're not using `Mirosoft.Data.Tools.Schema.SqlTasks.targets` at all. Would you mind sharing the contents of...

@jkonecki Based on the project file I think you're using Microsoft.Build.Sql, which is unrelated to MSBuild.Sdk.SqlProj. Have a look at [this repository](https://github.com/microsoft/DacFx/tree/main/src/Microsoft.Build.Sql) for more details on that. @Vikenesh I'm assuming...

This basically boils down to having the ability to `` a `.dacpac` from an arbitrary location on disk, much like how you can reference a `.dll` in C# projects. I'm...

Checking in binary files into Git is a bad practice since Git isn't very good at storing binary files. I guess you could use Git LFS to alleviate the pain,...