daohualiuxiang
/
AspNetCore.Docs
mirror of https://github.com/dotnet/AspNetCore.Docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update compatibility-version.md (#16145)

pull/16148/head
Rick Anderson 2019-12-11 10:28:42 -08:00 committed by GitHub
parent ec958a231e
commit ee53747f71
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
aspnetcore/mvc/compatibility-version.md
View File

@ -12,7 +12,7 @@ uid: mvc/compatibility-version
By [Rick Anderson](https://twitter.com/RickAndMSFT)
::: moniker range="= aspnetcore-3.0"
::: moniker range=">= aspnetcore-3.0"
The <xref:Microsoft.Extensions.DependencyInjection.MvcCoreMvcBuilderExtensions.SetCompatibilityVersion*> method is a no-op for ASP.NET Core 3.0 apps. That is, calling `SetCompatibilityVersion` with any value of <xref:Microsoft.AspNetCore.Mvc.CompatibilityVersion> has no impact on the application.
@ -56,4 +56,4 @@ For apps that encounter breaking behavior changes, using the appropriate compati
The <xref:Microsoft.AspNetCore.Mvc.MvcOptions> documentation has a good explanation of what changed and why the changes are an improvement for most users.
With ASP.NET Core 3.0, old behaviors supported by compatibility switches have been removed. We feel these are positive changes benefitting nearly all users. By introducing these changes in 2.1 and 2.2, most apps can benefit, while others have time to update.
::: moniker-end
::: moniker-end