Unknown switch ucr, use-current-runtime not working for restore, build and publish

[travnick]

Type of issue

Code doesn't work

Description

dotnet restore --ucr false
results with

MSBUILD : error MSB1001: Unknown switch.
    Full command line: 'C:\Program Files\dotnet\sdk\7.0.112\MSBuild.dll -maxcpucount -verbosity:m -nologo -target:Restore --ucr false -distributedlogger:Microsoft.DotNet.Tools.MSBuild.MSBuildLogger,C:\Program Files\dotnet\sdk\7.0.112\dotnet.dll*Microsoft.DotNet.Tools.MSBuild.MSBuildForwardingLogger,C:\Program Files\dotnet\sdk\7.0.112\dotnet.dll'
  Switches appended by response files:
Switch: --ucr

For switch syntax, type "MSBuild -help"

dotnet publish --use-current-runtime false looks like not working, since I see logs like

MSBuild version 17.4.8+6918b863a for .NET
  Determining projects to restore...
  1 of 3 projects are up-to-date for restore.
  MyProject -> D:\MyProject\Debug\net6.0\win-x64\MyProject.dll
  MyProject -> D:\MyProject\Debug\net6.0\win-x64\publish\

so it implicitly recognized win-x64 machine, but --use-current-runtime false should prevent this.

Page URL

https://learn.microsoft.com/en-us/dotnet/core/tools/dotnet-publish

Content source URL

https://github.com/dotnet/docs/blob/main/docs/core/tools/dotnet-publish.md

Document Version Independent Id

9439897e-dcb3-bc2e-5cae-35c1ca2e0681

Article author

@tdykstra

Metadata

• ID: 211afdc7-c796-202d-239d-823f2a499dff
• Product: dotnet-fundamentals

---

Associated WorkItem - 190727

[tdykstra]

@nagilson this option was documented in dotnet/docs#31970. Regarding --ucr we say in the doc

If the property is set to false, that implicit resolution will no longer occur.

If we don't implicitly use the current runtime, what runtime do we use?

[nagilson]

@nagilson this option was documented in dotnet/docs#31970. Regarding --ucr we say in the doc

If the property is set to false, that implicit resolution will no longer occur.

If we don't implicitly use the current runtime, what runtime do we use?

In this case, the application will be RID agnostic, so it will not be specific to one platform's runtime.

[tdykstra]

@travnick I can't repro the Unknown switch error, but I do see that --use-current-runtime false does not appear to be working correctly. So I'm going to transfer this issue to the SDK repo afs it's not a documentation issue.

[KalleOlaviNiemitalo]

Compare the implementation of --use-current-runtime to that of --self-contained:

sdk/src/Cli/dotnet/CommonOptions.cs

Lines 74 to 76 in bb5ae48

	public static Option<bool> CurrentRuntimeOption(string description) =>
	new ForwardedOption<bool>("--use-current-runtime", description)
	.ForwardAs("-property:UseCurrentRuntimeIdentifier=True");

sdk/src/Cli/dotnet/CommonOptions.cs

Lines 142 to 146 in bb5ae48

	public static Option<bool> SelfContainedOption =
	new ForwardedOption<bool>(
	new string[] { "--sc", "--self-contained" },
	CommonLocalizableStrings.SelfContainedOptionDescription)
	.ForwardAsMany(o => new string[] { $"-property:SelfContained={o}", "-property:_CommandLineDefinedSelfContained=true" });

--self-contained uses {o} to forward the option argument to MSBuild. --use-current-runtime instead always sets True as the property value.

Likewise, --interactive false behaves the same as --interactive true. However, --interactive does not seem to be documented as taking an argument, although the parser allows an argument.

sdk/src/Cli/dotnet/CommonOptions.cs

Lines 106 to 110 in bb5ae48

	public static Option<bool> InteractiveMsBuildForwardOption =
	new ForwardedOption<bool>(
	"--interactive",
	CommonLocalizableStrings.CommandInteractiveOptionDescription)
	.ForwardAs("-property:NuGetInteractive=true");

[KalleOlaviNiemitalo]

Perhaps public static ForwardedOption<T> ForwardAs<T>(this ForwardedOption<T> option, string value) should be replaced with public static ForwardedOption<bool> ForwardAs<bool>(this ForwardedOption<bool> option, string value) and changed to use value only when the option argument is true.

sdk/src/Cli/dotnet/OptionForwardingExtensions.cs

Line 15 in bb5ae48

public static ForwardedOption<T> Forward<T>(this ForwardedOption<T> option) => option.SetForwardingFunction((T o) => new string[] { option.Name });

T is bool in all of its uses anyway, and if the option passed to MSBuild does not depend at all on the argument of the ForwardedOption<bool>, that is likely to be a bug.

[KalleOlaviNiemitalo]

--use-current-runtime false not working could be considered part of #31646.