In .NET 6 the dotnet CLI has added a new dotnet sdk check command which performs a subset of what these helpers do, but the unfortunate side effect is that by adding the new command it ignores the global tool.
You can still invoke the tool directly with dotnet-sdk instead of dotnet sdk.
Once .NET 6 settles and the dotnet CLI has figured out what it's going to support, it may be interesting to choose a different command name here so it doesn't conflict with the built-in command. I don't have a suggestion as to what that should be at the moment.
In .NET 6 the
dotnetCLI has added a newdotnet sdk checkcommand which performs a subset of what these helpers do, but the unfortunate side effect is that by adding the new command it ignores the global tool.You can still invoke the tool directly with
dotnet-sdkinstead ofdotnet sdk.Once .NET 6 settles and the
dotnetCLI has figured out what it's going to support, it may be interesting to choose a different command name here so it doesn't conflict with the built-in command. I don't have a suggestion as to what that should be at the moment.