Hi Rick, I'm using your latest version of Client Tools for an integration project between two ERP softwares.

Everything was going fine until yesterday, when I received the latest version of the SDK from one of the software vendors, and it included and required version 12.0.3.23909 of Newtonsoft.Json.dll.

The new version of Newtonsoft.Json.dll causes a wwDotNetBridge "could not load file or assembly" error.

The latest version of Client Tools that I downloaded in December contained version 11.0.2.21924 of Newtonsoft.Json.dll. wwDotNetBridge version is 7.7.0.0. I am using .NET version 4.7.2.

I have tried using the Assembly Redirect method you have suggested in other posts, updating the old and new versions to reflect 12, but have had no success. In fact, when I apply the .config file, it also breaks the SDK from my other vendor, as well as still producing the wwDotNetBridge "could not load" error.

Thanks for any help you can give.

James Morris

The assembly redirects should work. Just make sure that:

• You're using the correct version in the redirect
• You're using the correct .config file (My.exe.config and/or vfp9.exe.config)

FWIW I was just thinking about this in the recent Web COnnection update, and decided to leave JSON.NET at 11.0.3 for this release and update in a future update to the latest to avoid possible complications.

+++ Rick ---

I think the version you need to use is:

<dependentAssembly>
  <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
  <bindingRedirect oldVersion="0.0.0.0-12.0.0.0" newVersion="12.0.0.0" />
</dependentAssembly>

The file version is 12.0.3, but the assembly version that is actually bound is 12.0.0 so that maybe why it wasn't working...

+++ Rick ---

Thanks Rick! That did it.
I learn something new every time you post a screenshot. That .NET Reflector is a really useful tool.

Thanks for your help!

James Morris