EasyHook adding the executing dir to the system path

[michaelgorman]

I have the easyhook..dll in a sub dir under the server exe that calls RemoteHooking.Inject and instead of the path to the sub dir where the easyhook.dll is the path to where the running exe / server is prefixed to the front of the system path, I think it is being done in RhInjectLibrary. It's creating a conflict for me because I have some dlls (not easyhook) that have the same names in the server dir as well as the injected app but the versions are different so the wrong dlls get loaded. Can this be changed to put the path where easyhook.dll resides instead?

[justinstenning]

@michaelgorman see this PR: #347

[michaelgorman]

@spazzarama I see the pull request is still open, do you know why the build failed? Seems like @UMU618 abandoned it, I would finish it but i dont have the knowledge working with the native build process

[UMU618]

Some EXEs need a current directory that is different with the parent folder of it. so we need a new API: RhCreateAndInjectEx to support passing current directory for the EXE.