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
Trying to use --property with dotnet watch test will fail, like this:
> dotnet watch --property:Foo=bar test
dotnet watch 🚀 Started
MSBUILD : error MSB1005: Specify a property and its value.
Full command line: 'C:\Program Files\dotnet\sdk\8.0.203\MSBuild.dll -maxcpucount -verbosity:m -restore -target:VSTest -nodereuse:false -nologo --property Verbose=true -property:VSTestArtifactsProcessingMode=collect -property:VSTestSessionCorrelationId=22404_8737de4d-5d82-4365-96d4-387349240da0'
Switches appended by response files:
Switch: --property
For switch syntax, type "MSBuild -help"
Note how the property isn't passed the same way it is given. MSBuild doesn't accept the format. Note how other properties are passed.
This works just fine.
>dotnet build --property:Foo=bar
This is the second bug I have found as part of the .NET 8 release that impacts the command line interface and the watch command specifically. Please invest in more rigorous testing of the CLI. Consider scripts that actually orchestrate command line interactions from the outside and don't just mock everything thinking that it will somehow be enough. It clearly hasn't been.
To Reproduce
Just run the following commands.
dotnet new console
dotnet watch --property:Foo=bar test
Describe the bug
Trying to use --property with dotnet watch test will fail, like this:
Note how the property isn't passed the same way it is given. MSBuild doesn't accept the format. Note how other properties are passed.
This works just fine.
This is the second bug I have found as part of the .NET 8 release that impacts the command line interface and the watch command specifically. Please invest in more rigorous testing of the CLI. Consider scripts that actually orchestrate command line interactions from the outside and don't just mock everything thinking that it will somehow be enough. It clearly hasn't been.
To Reproduce
Just run the following commands.
Further technical details
The text was updated successfully, but these errors were encountered: