Skip to content

Conversation

dsplaisted
Copy link
Member

In .NET 5, we automatically converted an OutputType of Exe to WinExe for WPF and Windows forms apps. This was intended to simplify .NET MAUI apps (so that the OutputType wouldn't need to be conditioned on the TargetFramework).

However:

  • This broke user expectations and frustrated some folks. See Revert DisableWinExeOutputInference #16563 and other linked issues
  • .NET MAUI apps are going to by default use WinUI, not Windows Forms or WPF, so this logic won't even apply to them

So this PR reverts the previous automatic OutputType conversion.

@mattleibow @jonathanpeppers @Redth The .NET MAUI targets for Windows should probably do something similar to the logic being removed here, ie change the OutputType from Exe to WinExe when targeting Windows.

@dsplaisted dsplaisted added the breaking-change Using this label will notify dotnet/compat and trigger a request to file a compat bug label Aug 11, 2021
@ghost ghost added the Area-NetSDK label Aug 11, 2021
@dsplaisted dsplaisted requested a review from a team August 12, 2021 05:53
@RussKie
Copy link
Contributor

RussKie commented Aug 16, 2021

To confirm - .NET 5.0 apps are still affected, but .NET 6.0+ aren't; and we don't intend to service .NET 5.0. Is this correct?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area-NetSDK breaking-change Using this label will notify dotnet/compat and trigger a request to file a compat bug

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants