You can try using the AddDllDirectory[^] method as the start of your application and add a directory containing the library for the current architecture. Just read the notes lower on the page on how to add the path to the default paths.
What do you get when you cross a joke with a rhetorical question?
The metaphorical solid rear-end expulsions have impacted the metaphorical motorized bladed rotating air movement mechanism.
Do questions with multiple question marks annoy you???
though I thought of handling the AppDomain.CurrentDomain.AssemblyResolve event and load my assembly with a path of my choosing.
Finding out whether the app is running as x86, x64, arm with GetType().Module.GetPEKind(out pek, out ifm);
I mean you need to run your program under the debugger to trap exactly where the error occurs, what the error is, and what variables, pointers etc. are possibly causing the fault. Without that information it is impossible to guess what may be going wrong.