From 29ccbaa0b096978e9c0ce040c84739f012c4fd7d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?C=C3=A9dric=20Luthi?= Date: Wed, 20 Feb 2019 12:39:25 +0100 Subject: [PATCH] Link to MvcOptions doc instead of source code (#11017) --- aspnetcore/mvc/compatibility-version.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/mvc/compatibility-version.md b/aspnetcore/mvc/compatibility-version.md index f01c2dc3e4..d55cdb430a 100644 --- a/aspnetcore/mvc/compatibility-version.md +++ b/aspnetcore/mvc/compatibility-version.md @@ -39,6 +39,6 @@ For apps that encounter breaking behavior changes, using the appropriate compati * Allows you to use the latest release and opt out of specific breaking behavior changes. * Gives you time to update your app so it works with the latest changes. -The [MvcOptions](https://github.com/aspnet/AspNetCore/blob/release/2.2/src/Mvc/Mvc.Core/src/MvcOptions.cs) class source comments have a good explanation of what changed and why the changes are an improvement for most users. +The documentation has a good explanation of what changed and why the changes are an improvement for most users. At some future date, there will be an [ASP.NET Core 3.0 version](https://github.com/aspnet/Home/wiki/Roadmap). Old behaviors supported by compatibility switches will be removed in the 3.0 version. We feel these are positive changes benefitting nearly all users. By introducing these changes now, most apps can benefit now, and the others will have time to update their apps.