Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
4 changes: 4 additions & 0 deletions docs/core/compatibility/2.1.md
Original file line number Diff line number Diff line change
Expand Up @@ -32,3 +32,7 @@ If you're migrating to version 2.1 of .NET Core, the breaking changes listed in
[!INCLUDE [DotNetCliToolReference project elements removed for bundled tools](../../../includes/core-changes/msbuild/2.1/dotnetclitoolreference.md)]

***

## See also

- [What's new in .NET Core 2.1](../whats-new/dotnet-core-2-1.md)
4 changes: 4 additions & 0 deletions docs/core/compatibility/3.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -378,3 +378,7 @@ If you're migrating to version 3.0 of .NET Core, ASP.NET Core, or EF Core, the b
[!INCLUDE[Default value of HttpRequestMessage.Version changed to 1.1](~/includes/core-changes/networking/3.0/httprequestmessage-version-change.md)]

***

## See also

- [What's new in .NET Core 3.0](../whats-new/dotnet-core-3-0.md)
4 changes: 4 additions & 0 deletions docs/core/compatibility/3.1.md
Original file line number Diff line number Diff line change
Expand Up @@ -39,3 +39,7 @@ If you're migrating to version 3.1 of .NET Core or ASP.NET Core, the breaking ch
[!INCLUDE[CellFormatting event](~/includes/core-changes/windowsforms/3.1/cellformatting-event-not-raised.md)]

***

## See also

- [What's new in .NET Core 3.1](../whats-new/dotnet-core-3-1.md)
4 changes: 4 additions & 0 deletions docs/core/compatibility/5.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -190,3 +190,7 @@ If you're migrating an app to .NET 5, the breaking changes listed here might aff
| - | - | - |
| [OutputType set to WinExe](sdk/5.0/automatically-infer-winexe-output-type.md) | ❌ | ✔️ |
| [WPF apps use Microsoft.NET.Sdk](sdk/5.0/sdk-and-target-framework-change.md) | ❌ | ✔️ |

## See also

- [What's new in .NET 5](../whats-new/dotnet-5.md)
4 changes: 4 additions & 0 deletions docs/core/compatibility/6.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -182,3 +182,7 @@ For information on other breaking changes for containers in .NET 6, see [.NET 6
| - | :-: | :-: | - |
| [XmlDocument.XmlResolver nullability change](core-libraries/6.0/xmlresolver-nullable.md) | ❌ | ✔️ | RC 1 |
| [XNodeReader.GetAttribute behavior for invalid index](core-libraries/6.0/xnodereader-getattribute.md) | ✔️ | ❌ | Preview 2 |

## See also

- [What's new in .NET 6](../whats-new/dotnet-6.md)
4 changes: 4 additions & 0 deletions docs/core/compatibility/7.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -154,3 +154,7 @@ If you're migrating an app to .NET 7, the breaking changes listed here might aff
| Title | Binary compatible | Source compatible | Introduced |
| - | :-: | :-: | - |
| [XmlSecureResolver is obsolete](xml/7.0/xmlsecureresolver-obsolete.md) | ❌ | ❌ | RC 1 |

## See also

- [What's new in .NET 7](../whats-new/dotnet-7.md)
5 changes: 5 additions & 0 deletions docs/core/compatibility/8.0.md
Original file line number Diff line number Diff line change
Expand Up @@ -69,3 +69,8 @@ If you're migrating an app to .NET 8, the breaking changes listed here might aff
| [TableLayoutStyleCollection throws ArgumentException](windows-forms/8.0/tablelayoutstylecollection.md) | Behavioral change | Preview 1 |
| [Top-level forms scale minimum and maximum size to DPI](windows-forms/8.0/forms-scale-size-to-dpi.md) | Behavioral change | Preview 1 |
| [WFDEV002 obsoletion is now an error](windows-forms/8.0/domainupdownaccessibleobject.md) | Source incompatible | Preview 1 |

## See also

- [What's new in .NET 8](../whats-new/dotnet-8.md)

2 changes: 1 addition & 1 deletion docs/core/docker/publish-as-container.md
Original file line number Diff line number Diff line change
Expand Up @@ -83,7 +83,7 @@ dotnet add package Microsoft.NET.Build.Containers

There are various configuration options available when publishing an app as a container. For more information, see [Configure container image](#configure-container-image).

By default, the container image name is the `AssemblyName` of the project. If that name is invalid as a container image name, you can override it by specifying a `ContainerImageName` as shown in the following:
By default, the container image name is the `AssemblyName` of the project. If that name is invalid as a container image name, you can override it by specifying a `ContainerImageName` as shown in the following project file:

:::code language="xml" source="snippets/Worker/DotNet.ContainerImage.csproj" highlight="8":::

Expand Down