Naomi's issue was likely different that what you're looking at. For her it was finding the right EXE to add the .config file to (the launching EXE) that allows access of the wwDotnetBridge.dll over a network.

To troubleshoot this start with the files locally (not on a network drive) and making sure the file is unblocked.

There is more information in this help topic:

Unable to load CLR Error in wwDotnetBridge


+++ Rick ---

>>>>In my own solution I just upgraded to the very latest version of Newtonsoft.Json.dll file which is version 11.02. However, I have lots of places where different versions of this dll are installed. I'm not sure where this particular version is coming from and what should I do to resolve this issue. Found a few threads on Stackoverlow with the same issue - sounds like I'm in the dll hell now.
>>>
>>>I suggest that you ask your question at https://support.west-wind.com/
>>
>>Thanks, Tore. Added a new question
>>
>>https://support.west-wind.com/Thread5AQ0B5KBT.wwt?rl=1#5AQ0B5KBU
>>
>>It is a big showstopper for me - I need to resolve it ASAP :(
>
>I saw your thread on .west-wind.com. I am having kind of the same problem with the wwDotNetBridge. But I don't use Newtonsoft.Json.dll.
>Was your solution tied to this dll?
>What was the solution?