Versioning of dependency on Microsoft.Extensions.Options

[maxmind]

Versioning of dependency on Microsoft.Extensions.Options

[oschwald]

Would you be able to expand on why this is necessary? That is a package reference to the NuGet package. Why do you need .NET 5.0?

[older]

@oschwald This NuGet package sets minimal version of Microsoft.Extensions.Options to version 5.0.0 so my function app is built with this version when I have reference on MaxMind.GeoIP2. But Azure Functions runtime is built with version 3.x and this version is loaded by runtime before my application starts. So as a result I get this exception. This is easily reproducible and happens not only when the app is deployed to Azure, but also if I run it locally using Azure Functions tools.

[kabilanvk]

Since .Net 5 for functions shows it's still in PREVIEW. I had to stick to 3.1 then reverting to MaxMind.GeoIP2 3.3.0 worked for me.

[older]

It is not only for functions. According to this comment from Microsoft's engineering manager for ASP.NET Core, Entity Framework, and Winforms, versions of extensions packages should match the major/minor of the ASP.NET Core.