Binding redirect issue -> Could not load file or assembly

[MichalGranat]

Hello,

I have WPF application targetting .net48 with following references:

A -> APP

A -> B -> APP

Both A & B references some other 3rd party lib (Microsoft.Extensions.Logging.Abstractions installed as nuget, let's nickname it L) .
Case is that B was referencing newer L than A. In result final APP build contains newer version of L.

When APP is launched as application everything works fine.

Issue is, that same *.dlls are used in TestStand in API. Unfortunatelly TS is throws following exception:

As B references L in version 8.0.2, there is this one in final build, I suppose. When A is tryining to use it, there is this exception.

Now, it's clear what's the issue, but I cannot find any reasonable solution. 
 -> Editing SeqEdit.exe.config is not acceptable for me
 -> Editing app.config seems to be without effect

Could someone provide any help, please?
Thanks and regards,
Michal

=======================

[esteban78]

---

@MichalGranat wrote:

Hello,

I have WPF application targetting .net48 with following references:

A -> APP

A -> B -> APP

Both A & B references some other 3rd party lib (Microsoft.Extensions.Logging.Abstractions installed as nuget, let's nickname it L) .
Case is that B was referencing newer L than A. In result final APP build contains newer version of L.

When APP is launched as application everything works fine.

Issue is, that same *.dlls are used in TestStand in API. Unfortunatelly TS is throws following exception:

As B references L in version 8.0.2, there is this one in final build, I suppose. When A is tryining to use it, there is this exception.

Now, it's clear what's the issue, but I cannot find any reasonable solution. 
 -> Editing SeqEdit.exe.config is not acceptable for me
 -> Editing app.config seems to be without effect

Could someone provide any help, please?
Thanks and regards,
Michal

=======================

---

The issue arises from version conflicts in referenced libraries. Ensure both A and B reference the same L version. Consider separate build configurations, assembly binding redirection, or isolated AppDomains.

[MichalGranat]

I've tried to setup assembly binding redirection, but without success. Where should I do this?

Question is why APP has no problem with this? Why TestStand is not able to handle it in the same way?