Closed ghost closed 8 months ago
For what it's worth, we're hitting this with dotnet test
and what would generate a binlog in .NET 6, e.g.
dotnet test /bl:LogFile=unittests.binlog
In .NET 7.0.100, no binlog is generated, which began breaking our builds when we were expecting to move some binlogs around for artifacts afterwards.
I believe we fixed this in 7.0.101's servicing release.
Describe the bug
Invoking a new project template from CLI fails with certain parameters passed to the template. This is a regression from previous version of the cli. There doesn't appear to be a clear workaround.
To Reproduce
simple_template\install.cmd
to install the custom templatebad-v7\repro.cmd
to invoke the template providing the-t
optionExpected: The command
dotnet new xyzzy -t Jane
should succeed, as-t
should match thetortoise
parameter to thexyzzy
template. This is the result on dotnet sdk 6.0Actual: The command
dotnet new xyzzy -t Jane
on net sdk 7.0 fails with invalid arg, indicating that-t
must beproject
. The-t
argument was inappropriately gobbled up by thedotnet new
command, when it should have been a parameter to thexyzzy
template instead.Exceptions (if any)
Further technical details
Example console output from running good-v6\repro.cmd and bad-v7.cmd, illustrating reproing the bug. Note that only commands ending in
.cmd
were user entered commands.