I'm not sure exactly why this happens, I think it's something to do with
how the .NET runtime itself delay-loads assemblies and the rules it has
for looking for dependent dll's
There are three ways I know of to work around this:
1. Use Dir.chdir to switch your working directory to
Orion Edwards wrote in post #1072378:
I'm not sure exactly why this happens, I think it's something to do with
how the .NET runtime itself delay-loads assemblies and the rules it has
for looking for dependent dll's
There are three ways I know of to work around this:
1. Use Dir.chdir to
