Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update version info for breaking change #21959

Merged
merged 1 commit into from
Dec 14, 2020
Merged

Update version info for breaking change #21959

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions .../core/compatibility/windows-forms/5.0/automatically-infer-winexe-output-type.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,15 +9,15 @@ ms.date: 09/18/2020

## Change description

In previous versions of .NET, the value that's specified for `OutputType` in the project file is used. For example:
In previous versions of the .NET SDK, the value that's specified for `OutputType` in the project file is used. For example:

```xml
<PropertyGroup>
<OutputType>Exe</OutputType>
</PropertyGroup>
```

Starting in .NET 5.0, `OutputType` is automatically set to `WinExe` for WPF and Windows Forms apps. For example:
Starting in the 5.0.1 version of the .NET SDK, `OutputType` is automatically set to `WinExe` for WPF and Windows Forms apps that target any framework version, including .NET Framework. For example:

```xml
<PropertyGroup>
Expand All @@ -31,7 +31,7 @@ It's assumed that most users don't want a console window to open when a WPF or W

## Version introduced

.NET 5.0
.NET 5.0.1

## Recommended action

Expand Down