Breaking change in response file parsing
See original GitHub issueDescribe the bug
Since upgrading from SDK 6.0.300
to 6.0.301
, the response file parsing logic has changed, where
-p:VSTestTestAdapterPath=".;C:\BuildAgent\plugins\dotnet\tools\vstest15"
used to work, but now shows an error:
dotnet build .\IPFX.UC.PresenceServer.sln @C:\BuildAgent\temp\agentTmp\1.rsp
Microsoft (R) Build Engine version 17.2.0+41abc5629 for .NET
Copyright (C) Microsoft Corporation. All rights reserved.
MSBUILD : error MSB1006: Property is not valid.
Switch: C:\BuildAgent\plugins\dotnet\tools\vstest15
For switch syntax, type "MSBuild -help"
To Reproduce
docker run -it --rm mcr.microsoft.com/dotnet/sdk:6.0.301 bash
mkdir repro
cd repro
dotnet new console
echo "-p:VSTestTestAdapterPath=\".;/opt/buildagent/plugins/dotnet/tools/vstest15\"" > params.rsp
dotnet restore repro.csproj @params.rsp
Exceptions (if any)
MSBUILD : error MSB1006: Property is not valid.
Switch: /opt/buildagent/plugins/dotnet/tools/vstest15
For switch syntax, type "MSBuild -help"
Expected
Determining projects to restore...
All projects are up-to-date for restore.
Further technical details
- Include the output of
dotnet --info
# dotnet --info
.NET SDK (reflecting any global.json):
Version: 6.0.301
Commit: 43f9b18481
Runtime Environment:
OS Name: debian
OS Version: 11
OS Platform: Linux
RID: debian.11-arm64
Base Path: /usr/share/dotnet/sdk/6.0.301/
Host (useful for support):
Version: 6.0.6
Commit: 7cca709db2
.NET SDKs installed:
6.0.301 [/usr/share/dotnet/sdk]
.NET runtimes installed:
Microsoft.AspNetCore.App 6.0.6 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 6.0.6 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET runtimes or SDKs:
https://aka.ms/dotnet-download
- The IDE (VS / VS Code/ VS4Mac) you’re running on, and its version N/A
Issue Analytics
- State:
- Created a year ago
- Reactions:33
- Comments:18 (9 by maintainers)
Top Results From Across the Web
When Is A Change A Breaking Change For An API
Changing error types, messages, and other details. It could also mean performing string-parsing on the extended data provided in an error. As ...
Read more >Breaking changes in .NET 6
NET 6, the breaking changes listed here might affect you. Changes are grouped by technology area, such as ASP.NET Core or Windows Forms....
Read more >c# - Parse file differently upon different version
EDIT : I've done some research about this, but have not been able to find a solution! I'm reading a configuration from an...
Read more >Deprecations and removals by version | GitLab
Each deprecated feature will be removed in a future release. Some features cause breaking changes when they are removed. On GitLab.com, deprecated features...
Read more >Common API mistakes and how to avoid them
One of the worst things we can do to an API is to release a backwards-breaking change. As a rule of thumb, adding...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Reopening this due to repro.
Good point, 6.0.305 and 6.0.402 should contain the fix. ‘and up’ was intended to mean ‘the higher feature bands’, which right now are 6.0.4xx and 7.0.1xx.