MSBuild.Sdk.SqlProj
MSBuild.Sdk.SqlProj copied to clipboard
rr-wfm
Allow sql projects to publish on build (PublishOnBuild).
How is this different from
dotnet build
dotnet publish
especially since we support publish for local development only
It allows this to be published even if the sqlproj just happens to be part of a solution where publishing those projects might fail (because they depend on runtimes for which the only supported form of publish is FDD). Also, it acts as a shortcut for when you only want to run build on the entire solution and do not want to run publish on the entire solution as well (however you want to publish specific projects in it via cli).
I do not understand this sentence: because they depend on runtimes for which the only supported form of publish is FDD - what is FDD?
Also, it acts as a shortcut for when you only want to run build on the entire solution and do not want to run publish on the entire solution as well (however you want to publish specific projects in it via cli).
How is that very different from just
dotnet build
dotnet publish
I do not understand this sentence: because they depend on runtimes for which the only supported form of publish is FDD - what is FDD?
Also, it acts as a shortcut for when you only want to run build on the entire solution and do not want to run publish on the entire solution as well (however you want to publish specific projects in it via cli).
How is that very different from just
dotnet build dotnet publish
Framework dependent deployment (or FDD). I think dotnet publish now specifies an implicit RID since the release of the .NET 7 SDK which implies self-contained which can be breaking for some projects 💀.