Aspnetcore 3.1 with OData

If you’re creating a bug/problem report, please include followings:

• Your Abp package version. - 5.2
• Your base framework: .Net Core. 3.1

Aspnetboilerplate Angular Template 5.2

Integration with the explanation from the page: https://aspnetboilerplate.com/Pages/Documents/OData-AspNetCore-Integration

in .net core 3.1 mvc.internal is removed:

Could not load type 'Microsoft.AspNetCore.Mvc.Internal.ActionConstraintCache' from assembly 'Microsoft.AspNetCore.Mvc.Core, Version=3.1.1.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'.'

// Configure Abp and Dependency Injection
return services.AddAbp<OdataWebHostModule>(
    // Configure Log4Net logging
    options => options.IocManager.IocContainer.AddFacility<LoggingFacility>(
        f => f.UseAbpLog4Net().WithConfig("log4net.config")
    )
);

Do you found any workaround?

It worked with .net Core 3.1 Standard project template without endpoints:

public void ConfigureServices(IServiceCollection services)
{
    services.AddControllers(mvcOptions =>
       mvcOptions.EnableEndpointRouting = false);

    services.AddOData();
}

app.UseMvc(routeBuilder =>
{
    routeBuilder.Select().Filter();
    routeBuilder.MapODataServiceRoute("odata", "odata", GetEdmModel());
});

//app.UseEndpoints(endpoints =>
//{
//    endpoints.MapControllers();
//});

[maliming]

@ryancyq #5196 just updated a package, we have not released the Abp.AspNetCore.OData package and updated the documentation and examples.

[ismcagdas]

@maliming yes, the related issue https://github.com/OData/WebApi/issues/1748 was open when we move to ASP.NET Core 3.0. It seems like now it supports .NET Core 3.x. We can implement this in 5.4, what do you think ?