From ee53747f71e052d3ec57ca6cb11333fc8334d8ae Mon Sep 17 00:00:00 2001 From: Rick Anderson <3605364+Rick-Anderson@users.noreply.github.com> Date: Wed, 11 Dec 2019 10:28:42 -0800 Subject: [PATCH] Update compatibility-version.md (#16145) --- aspnetcore/mvc/compatibility-version.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/aspnetcore/mvc/compatibility-version.md b/aspnetcore/mvc/compatibility-version.md index c0bf454fc1..265d3e2b98 100644 --- a/aspnetcore/mvc/compatibility-version.md +++ b/aspnetcore/mvc/compatibility-version.md @@ -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 method is a no-op for ASP.NET Core 3.0 apps. That is, calling `SetCompatibilityVersion` with any value of has no impact on the application. @@ -56,4 +56,4 @@ For apps that encounter breaking behavior changes, using the appropriate compati The 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 \ No newline at end of file +::: moniker-end