Consider: drop mono support for .NET Framework apps

[Youssef1313]

sdk/src/Tasks/Microsoft.NET.Build.Tasks/targets/Microsoft.NET.Sdk.targets

Lines 1440 to 1443 in f578225

	<PropertyGroup Condition="$([MSBuild]::IsOSUnixLike())">
	<RunCommand Condition="'$(RunCommand)' == ''">mono</RunCommand>
	<RunArguments Condition="'$(RunArguments)' == ''">&quot;$(TargetPath)&quot; $(StartArguments)</RunArguments>
	</PropertyGroup>

Should we consider dropping this? cc @baronfel @jkotas

Today, running dotnet run on a console app that's .NET Framework on non-Windows will run it via mono. Is that scenario still supported or used by enough people?

[jkotas]

It would make sense to me to start dropping support for unsupported scenarios like this one. It is not a good use of resources to carry this baggage around, and the support is likely broken in number of ways anyway.

The problem is that SDK does not have any depreciation policy currently - see discussion #51765 (comment) and so it is impossible to drop anything. I do not think that it is sustainable long-term. cc @marcpopMSFT

[dotnet-policy-service]

Refer to the .NET SDK breaking change guidelines

[ViktorHofer]

Also see the discussion in microsoft/vstest#15340 (comment) for the (probably non-existent) impact on VSTest.

[marcpopMSFT]

From telemetry, it's fewer than 300 run calls in the past 30 days that specify a netfx TFM and run on non-windows (out of ~1M calls that specify TFM so ~.5%). This wouldn't include distro customers or customers that have the TFM not specified on the CLI.

Seems like this is low enough that we can announce early in 11 and remove. We should detect and direct customers on instructions on how to get unblocked.