You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My CI pipelines add build properties via the CLI option -p and use a semicolon (;) as a delimiter between multiple key-value pairs.
E.g. dotnet pack MyProject.csproj -c Release "-p:Foo=bar;PackageVersion=1.2.3-baz"
However, upon updating my .NET SDK version in the global.json file from 6.0.300 to 6.0.400, I noticed that my package versions were incorrect. Looking into it more, it seems like this has been broken since 6.0.301.
To Reproduce
I've been testing this on .NET 6 projects using versions 6.0.300, 6.0.301, and 6.0.400 of the SDK. You're welcome to use my own OSS project which has a single global.json file at the root of the repository: https://github.com/wsugarman/sweetener/blob/main/src/Core/Sweetener/Sweetener.csproj, but it should reproduce in a new .NET 6 library template. Simply toggle between different versions of the .NET SDK.
Describe the bug
My CI pipelines add build properties via the CLI option
-p
and use a semicolon (;
) as a delimiter between multiple key-value pairs.E.g.
dotnet pack MyProject.csproj -c Release "-p:Foo=bar;PackageVersion=1.2.3-baz"
However, upon updating my .NET SDK version in the
global.json
file from 6.0.300 to 6.0.400, I noticed that my package versions were incorrect. Looking into it more, it seems like this has been broken since 6.0.301.To Reproduce
I've been testing this on .NET 6 projects using versions 6.0.300, 6.0.301, and 6.0.400 of the SDK. You're welcome to use my own OSS project which has a single
global.json
file at the root of the repository: https://github.com/wsugarman/sweetener/blob/main/src/Core/Sweetener/Sweetener.csproj, but it should reproduce in a new .NET 6 library template. Simply toggle between different versions of the .NET SDK.Worked previously, but now doesn't >= 6.0.301
Continues to work
Further technical details
The text was updated successfully, but these errors were encountered: