No Plugin will Install

[jsdanie1]

Bug: When installing I believe any plugin, I keep getting:

"Could not load file or assembly 'Microsoft.Bcl.AsyncInterfaces, Version=6.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies. The system cannot find the file specified."

To Reproduce
Go to Tool Store, Install any Plugin

Expected behavior
It normally installs, I use this all the time, It appears maybe a recent Windows Update broke this? Was working just fine the other day.

Use this tool at least once or twice per day lol, so really need to get it working again :(

[daryllabar]

What version of the XrmToolBox are you using?

[jsdanie1]

I'm using the latest one, tried the following troubleshooting.

• I tried downloading a fresh copy.
• I tried clearing out %AppData%\Roaming\MscrmTools\XrmToolBox so it would be on a fresh setup.
• I've tried even installing a version previous, but still the same issue on both.

xrmtoolbox-v1.2023.12.68

[daryllabar]

This is due to the XTB updating it's version of the Microsfot.Bcl.AsyncInterfaces to 7.0 and updating how it loads dependent dlls. Whatever plugin you're installing has a dependency on the older version. You should reach out to the plugin maker (I know the Plugin Registration Tool was having this issue and a PR was completed a couple hours ago with a fix) and let them know the issue. You have a couple work arounds.

1. Install XTB 1.2022.10.58
2. Replace the Microsfot.Bcl.AsyncInterfaces in the XTB folder with the 6.0 version
3. Add an assembly binding redirect to the XTB.exe.config to redirect 6.0 to 7.0 (@MscrmTools not sure how many plugins are having this issue, but this may be something to look into. I do know that it has the potential to cause issues with some plugins though. Recently I ran into an issue in the EBG were I was attempting to reference a newer version of the Microsoft.Xrm.Sdk, but because it was only minor version difference, the 0.0.0.0-9.0.0.0 override was preventing it from loading... )

[jsdanie1]

I will try and relay that information to each developer. That seems like a pretty big change if its impacting alot of the core plugins I use. I'm not entirely sure about doing steps 2 and 3, or how to do 3 at all lol

Although today its back to working? So idk what happened.