0

Anyone experience an unexpected issue when upgrading your IdentityModel package dependencies? Is this a "bug" or is there another way to get around this?

I have several .NET 4.8.1 framework console apps that have a dependency on the IdentityModel package, which has always been a collection of these packages:

Microsoft.IdentityModel.JsonWebTokens 
Microsoft.IdentityModel.Logging       
Microsoft.IdentityModel.Tokens       
System.IdentityModel.Tokens.Jwt

Our most recent packages were on 6.19. Nuget showed that 6.23.1 was available. So I let it "update" the packages... which suddenly pulled in MANY more packages (that were NOT shown as dependencies):

Microsoft.IdentityModel.Abstractions   
Microsoft.Bcl.AsyncInterfaces          
System.Buffers                         
System.Memory                          
System.Numerics.Vectors                
System.Runtime.CompilerServices.Unsafe 
System.Text.Encoding                   
System.Text.Encodings.Web              
System.Text.Json                       
System.Threading.Tasks.Extensions      
System.ValueTuple
Margo Noreen
  • 396
  • 1
  • 3
  • 12

1 Answers1

0

We can see the difference between the dependencies of the two versions：

6.19.0 enter image description here 6.26.1 enter image description here

And when we update this package we can see that: enter image description here

So I think this is normal, it is caused by the change in the dependencies of the Microsoft.IdentityModel.Tokens package

Jingmiao Xu-MSFT
  • 2,076
  • 1
  • 3
  • 10
  • Thank you for your reply. I think this confirms that a LOT of new dependencies were added, but I don't consider this a "good answer"... the dependency chain seems to be getting a bit out of control. DLL-heck has returned. – Margo Noreen Oct 02 '22 at 18:27