Embedded Reference only working once

[sh_jackland]

I think I know what's happening. The error message I'm getting is it can't find Version=6.22.0, but .dll version I'm using is 6.25.1

In the Visual Studio project, I first installed Microsoft.Identity.Client which then installed version 6.22.0 of Microsoft.IdentityModel.Abstractions as a dependency.
I then updated Microsoft.IdentityModel.Abstrations to version 6.25.1. Microsoft.Identity.Client says it can use versions >=6.22.0 and verified this in the project.

I then used these .dll files for Embedded Reference.

In the Microsoft.Identity.Client.dll, it's References has the version of Microsoft.IdentityModel.Abstrations specified as 6.22.0

When it searches for the assembly, it must also be checking the version but instead of doing a >=, it's just doing ==.
Although it's strange that everything works the first time.

It seems the solution is to use the exact version.

[SBarnes]

You may be correct but the interesting thing is Jiwa's original call to load embedded references uses System.Reflection.Assembly.LoadFile and the resolver is using System.Reflection.Assembly.LoadFrom.

Mike any thoughts on the different calls?

[Mike.Sheen]

You may be correct but the interesting thing is Jiwa's original call to load embedded references uses System.Reflection.Assembly.LoadFile and the resolver is using System.Reflection.Assembly.LoadFrom.

Mike any thoughts on the different calls?

It's been a while since I had to sort out the intricacies, but the Plugin business logic uses LoadFile to obtain the embedded reference full name (but not actually load it) we then use Assembly.Load(FullName) to actually load the assembly.

LoadFile is used because we don't want any ambiguity on where to find the assembly. We know exactly where it is, but we don't actually load that assembly - we then use Assembly.Load(FullName) because another assembly might have already loaded the same exact assembly from another plugin folder location - so by using FullName it prevents trying to load the same assembly twice into the application domain which would cause an error.

I've not been able to repro the OP's issue - so I'm a bit in the dark as to why it was presenting a problem.

[SBarnes]

So here is an interesting question what happens if two plugins were using the same third party library but different versions something like say two versions of Newtonsoft can both exist in the same app domain given the use of the full name?

[Mike.Sheen]

So here is an interesting question what happens if two plugins were using the same third party library but different versions something like say two versions of Newtonsoft can both exist in the same app domain given the use of the full name?

I would need to test this to be sure, but my belief is if the full name is the same, then it won't load it a second time, it uses the one previously loaded into the application domain.

[SBarnes]

I had assumed you would say that and that would be the actual case but it appears we are both wrong 7.2.1 will load two plugins one with 13.01 and one with 13.02 of Newtonsoft and happily deserialize JSon.

Start up reports both plugins as loaded and no exceptions and under programdata there are the correct versions in each directory.