I am making a DLL extension that uses the Azure SDK libraries in .NET framework 4.6 to an existing program.I had the program developers compile the program adding a reference to my DLL earlier, however, after i compiled it and run it, it appears that it attempts to load two different versions of Azure.Core at the same time: 1.42, the one which is referenced in the project, and 1.39 the one which Azure.ResourceManager specifies in the nuget package view in Visual Studio ">=1.39". The same will happen for Azure.ResourceManager 1.12 and 1.13 (likely referenced by one of the ResourceManager submodules).My understanding was that with binding redirects, this shouldn't happen because at runtime the 1.42 or whatever version i specified should be the only one marked as valid.
What I tried:
- Placed ALL the libraries in the build folder of my extension in the folder of the program executable
- I double checked the app.config, made sure that binding redirects were enabled and correctly pointed (including the public key) and recompiled multiple times
- adding the binding redirects to machine.config on the computer
- running it on a different computer with the same program (same issue)
- changing Azure.Core/RM dll version (the error swaps versions as well)
I don't know what else to try at this point.