Different options in `ApiVersioningOptions.cs` between .NET Framework and .NET Core packages

[Saibamen]

Different options in `ApiVersioningOptions.cs` between .NET Framework and .NET Core packages

[commonsensesoftware]

This option still exists, but it is now only set through dependency injection (DI). Web API doesn't have out-of-the-box DI support so the option needs to be explicit in the options. In ASP.NET Core, Minimal APIs and MVC Core are separated by the AddApiVersioning() and AddMvc() respectively. I considered moving ControllerNameConvention over to the MVC Core options, but I really wanted to reduce the number of configurable options which are better suited for DI. In fact, the naming convention could always be set via DI. Setting it via the options was a secondary way.

You can find the source at:

aspnet-api-versioning/src/AspNetCore/WebApi/src/Asp.Versioning.Mvc/DependencyInjection/IApiVersioningBuilderExtensions.cs

Line 66 in 471eb04

services.TryAddSingleton<IControllerNameConvention, DefaultControllerNameConvention>();

To achieve your desired configuration, you need only set or replace the service you want to use:

builder.Services.AddSingleton<IControllerNameConvention, OriginalControllerNameConvention>();

In fairness, I missed adding this change to the migration guide. I have updated the section on configuration to note this difference.

I hope that helps.

[Saibamen]

Thank you. It works :)