Passing properties with multiple values stops woring with net7 RC1 - 7.0.100-rc.1.22431.12
Issue Description
Hi - in our csproj files use use custom properties for additional AssemblySearchPaths, see below where we added $(ReferencePath).
<AssemblySearchPaths>$(AssemblySearchPaths);$(ReferencePath);$(OutputPath);$(OutputPath)\Server</AssemblySearchPaths>
Now we start a build an pass in the ReferencePath:
dotnet.exe build test.sln --configuration Release /property:ReferencePath="C:\123;C:\456"
with NET6 - when doing an verbose build - we get this:
SearchPaths:
{CandidateAssemblyFiles}
{HintPathFromItem}
{TargetFrameworkDirectory}
{RawFileName}
C:\123
C:\456
now with NET7 RC1 SDK - we get this:
SearchPaths:
{CandidateAssemblyFiles}
{HintPathFromItem}
{TargetFrameworkDirectory}
{RawFileName}
C:\123;C:\456
See the values are not split anymore - and the paths are not working? Any info about this behaviour?
thx
Duplicate of dotnet/sdk#27059
thx for the fast reply. I see this was fixed in 6.0.x - so will this com to 7.0.x ?
@noxe Yes, I believe it'll be in RC2.
thank you!
So - i tested this with .NET SDK 6.0.401 - but this still does not work @rainersigwald:
"C:\Program Files\dotnet\sdk\6.0.401"
command:
dotnet build buildprop.sln -p:ReferencePath="c:\test;c:\test1"
or
dotnet build buildprop.sln -p:ReferencePath="c:\test,c:\test1"
does NOT split the paths:
SearchPaths:
{CandidateAssemblyFiles}
{HintPathFromItem}
{TargetFrameworkDirectory}
{RawFileName}
c:\test;c:\test1
@noxe please report that in the SDK bug.
Moving to the dotnet/sdk repo, as the semicolon-delimiting aspect of values is the particular regression here.
I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.
Apologies for this @noxe - we've got a PR up for this that we will work on including in a servicing fix for this series of SDKs and onwards.
thx you for the Update!
closing as the linked PRs are in.