Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Breaking change to passing multiple properties as /p:P1=V1;P2=V2

See original GitHub issue

I believe this was changed by https://github.com/dotnet/cli/pull/9153

Steps to reproduce

Create test.proj with the following content

<Project>
  <Target Name="Build">
    <Message Importance="High" Text="A: $(A)" />
    <Message Importance="High" Text="B: $(B)" />
  </Target>
</Project>

dotnet build test.proj /p:A=1;B=2 /nologo /clp:NoSummary

Expected behavior

  A: 1
  B: 2

Actual behavior

  A: 1;B=2
  B:

Environment data

.NET Core SDK (reflecting any global.json):
 Version:   2.2.100-preview1-008941
 Commit:    dae5099ffb

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.17134
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   d:\src\s\sdk\.dotnet\sdk\2.2.100-preview1-008941\

Host (useful for support):
  Version: 2.1.0-rtm-26515-03
  Commit:  caa7b7e2ba

.NET Core SDKs installed:
  2.2.100-preview1-008941 [d:\src\s\sdk\.dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.0-rtm-30752 [d:\src\s\sdk\.dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.0-rtm-30752 [d:\src\s\sdk\.dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 1.0.5 [d:\src\s\sdk\.dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 1.1.2 [d:\src\s\sdk\.dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.0 [d:\src\s\sdk\.dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.0-rtm-26515-03 [d:\src\s\sdk\.dotnet\shared\Microsoft.NETCore.App]

To install additional .NET Core runtimes or SDKs:
  https://aka.ms/dotnet-download

Issue Analytics

State:
Created 5 years ago
Comments:10 (10 by maintainers)

Top GitHub Comments

1reaction

rainersigwaldcommented, May 30, 2018

I’m ready to commit to that. I think it’s the least-bad option. @AndyGerlicher objections?

1reaction

peterhuenecommented, May 30, 2018

Ah, I see the crux of the problem then. If MSBuild decided on option 4, then I’d be in favor of reverting dotnet/cli#9153 and ask users to do the same for dotnet (escape quotes around the property value) and to not try anything fancy from our side.