Closed FIELDPOINT closed 2 years ago
The important difference I noticed between versions 4.2.0 and 4.2.1 is that all package references are now scoped to the .NET Framework 4.5. So it does not work correctly when I reference packages from another (compatible) target framework. Not sure this is the case, just FYI.
FYI, My workaround atm is using the BindingRedirect on the Web.config file which works.
Binding redirects are generally required when updating a dependency version like this, but I thought nuget was supposed to generate them for you.
Thanks for the tip. I was wondering if someone would know just why/where is the older version being called from.
These libraries were all compiled against 5.3.0, that's what they're expecting at runtime. The binding redirects are required to override that. https://github.com/aspnet/AspNetKatana/blob/beb224c88712b08ce45f1d14bb8cf0cd9d4a8503/eng/Versions.props#L14
I see. Thanks for clearing that up.
I have a .NET framework 4.8 based ASP.NET Webforms application that has implemented Azure authentication using version v6.08.0.0 of these Micorsoft.IdentityModel and v4.1.1 of Microsoft.owin assemblies. My visual studio project compiles successfully but throw’s the exception noted below when the assembly Microsoft.IdentityModel.Tokens is used.
I am seeing an issue where the wrong version of the assembly is being called by Microsoft.Owin.Security.OpenIdConnect, Version=4.1.1.0. But Microsoft.Owin.Security.OpenIdConnect should allow for => 5.3.0.0 of Micorsoft.IdentityModel assemblies.
I have spent an entire day troubleshooting this. Hope someone is able to shed some light on this. Thank you.
FYI, My workaround atm is using the BindingRedirect on the Web.config file which works.
Here is the Error, Stack Trace and the Full Dependency Stack.
Error
Assembly Trace
Stack Trace
Project File
Dependency Stack