Microsoft.Extensions.Logging

[TysonMN]

Serilog.AspNetCore currently depends on version 2.0.0 of Microsoft.Extensions.Logging. The latest version of Microsoft.Extensions.Logging is 2.2.0.

In order to remove a binding redirect from my code, could a new version of Serilog.AspNetCore be released that depends on this latest version of Microsoft.Extensions.Logging?

[svrooij]

As stated in the Instructions. You should use Install-Package Serilog.AspNetCore -DependencyVersion Highest which should install the highest Version of the dependencies.

That should help for now at least

[TysonMN]

Hello @svrooij. Thanks for your suggestion.

I just followed your instructions and executed the command you provided in new solution/project. As you can see in this screenshot, the version of Microsoft.Extensions.Logging installed is still just 2.0.0.

Is this the behavior you expected? If so, how does this answer the question in my original post? If not, what behavior did you expect?

I am not completely sure what you or Microsoft (here) mean by "highest version" when stated as you both did without any explicit qualifications. The definition I expect in the absence of any qualifications is the "maximum" version among released versions. In the case of Microsoft.Extensions.Logging, this "maximum" released version is currently 2.2.0, so something is not right.

I have a guess, but I could be wrong. My guess is that both you and Microsoft are implicitly including a qualification in the form of a restrictions imposed by the installed package(s). Currently, Serilog.AspNetCore specifies that it depends on precisely version 2.0.0 of Microsoft.Extensions.Logging. So in the case of installing Serilog.AspNetCore via the command Install-Package Serilog.AspNetCore -DependencyVersion Highest and focusing on the dependency Microsoft.Extensions.Logging, the option -DependencyVersion Highest means the "maximum" version contain in the intersection of the set of all released versions of Microsoft.Extensions.Logging and the set of versions of Microsoft.Extensions.Logging allowed by Serilog.AspNetCore, which is just the singleton set containing version 2.0.0. This guess is consistent with the fact that executing the command Install-Package Serilog.AspNetCore -DependencyVersion DependencyVersionOption for all values of DependencyVersionOption (namely Lowest, HighestPatch, HighestMinor, and Highest) all install version 2.0.0 of Microsoft.Extensions.Logging.

[nblumhardt]

@bender2k14 if you add an explicit dependency on M.E.Logging version 2.2 to your own CSPROJ, that's the version you'll end up building against. This package works with any of the 2.x MEL versions, the binding redirect is just how this ends up manifesting on the .NET Framework, I think.

[TysonMN]

This package works with any of the 2.x MEL versions

Can you state this programmatically in your code?

Currently your code says otherwise. It says that it only works with version 2.0.0:

PackageReference Include="Microsoft.Extensions.Logging" Version="2.0.0"

One way to state this programmatically in your code is to change that line to

PackageReference Include="Microsoft.Extensions.Logging" Version="2.*"

See this documentation for more examples and explanation.

[adamchester]

I think we have already stated it programmatically by using “2.0.0”. In NuGet, this means >= 2.0.0

[TysonMN]

@adamchester I would believe you if your code specified the dependent version as 2.0. Instead, your code specifics the dependent version as 2.0.0.

[nblumhardt]

Hi @bender2k14 - the docs are pretty tough to interpret precisely, in this regard, but the notation x.y or x.y.z is a minimum-version spec. If you want to specify an exact version, it's [x.y] or [x.y.z]. (Per the link you provided above.)

If you expand "Dependencies" for this package on NuGet.org you'll see it called out explicitly: https://www.nuget.org/packages/serilog.aspnetcore

We tried the 2.* wildcard option earlier and broke some builds: subtly, version wildcards are resolved at package build time and not at install time, so specifying 2.* got us a fixed 2.2.0 dependency in the package itself (discussion).

Specifying the desired version of MEL from your own CSPROJ alongside your reference to this package will always get you the version you want.

HTH

[TysonMN]

Oh, that's good. That makes things a bit easier.

I see that your NuGet file...
https://www.nuget.org/packages/Serilog.AspNetCore/2.1.1
...does explicitly say that it works with version 2.0.0 or greater.

I still want to figure out why my tests above didn't install the latest version :/

Thanks for all your patience with me :)

[nblumhardt]

Thanks @bender2k14 👍