Hi,
the above answer would work if the library mentioned by OP (TolkDotNet.dll) is unmanaged/native winPE that exports symbols. I suspect that is not the case (I did not bother to google since the name says it all) - so this TolkDotNet.dll seems to use other native libraries using interop and would load appropriate runtime based on the platform being invoked on.
that said - you can consider a commercial/free obfuscator tool (I have experience with redgate SmartAssembly) and it allowed me to bundle all custom dependencies in a single executable file/dll with the dependencies embedded as encrypted binary blobs within the main assembly.
i hope that helps you assess your options -
- The x86/64 folder needs to exist wherever the tolkdotnet.dll is , and it can not be the GAC so
- add a manifest file and specify the folder you would like to load this DLL from - it can be any folder on the file system - even outside your solution- however that would create a deployment chore for you to ensure that you package and deploy the same configuration to a target machine (maybe it’s not even required in OPs scenario so I would leave it at that)