Upgrading Microsoft.AspNetCore.Mvc.Versioning 3 to 4
Breaking3.1.6 → 4.2.0Breaking3Platform2New14Changed5Fixed29Other10
BreakingUpgrade verdict
3 breaking changes and 2 platform requirement changes.
In plain terms
- The old UseQualifiedOperationNames option is gone; use the new option instead.
- The old UseQualifiedOperationNames option is gone; use the new option instead.
- The conventions API was restructured, which may break existing code that uses it.
- This version now requires .NET Core 3.1 and no longer works with ASP.NET Core 2.2.
Must act 5 items need code or config changes
Target frameworks requirement changed in 4.1.1: .NETStandard2.0 → .NETCoreApp3.1.
What you must change
Breaking3
Removes the obsolete UseQualifiedOperationNames option.
UseQualifiedOperationNamesRemoves the obsolete UseQualifiedOperationNames option for ASP.NET Core with OData.
UseQualifiedOperationNamesRefactors the conventions API so interfaces are defined end-to-end.
Platform2
Targets .NET Core 3.1 for all ASP.NET Core flavors, including OData, and drops support for ASP.NET Core 2.2.
Adds support for ASP.NET Core 3.0.