The FileMonitor example does not work for me, just showing this line and then exit.
Looking through the source code, it seems to be trying to locate runtime configuration with enviorment variable CORE_ROOT_64, CORE_ROOT_32(which is pretty unreliable?).
Can we inject a C++/CLI dll to the target process and let windows handle the runtime loading instead of manually locating it?
The FileMonitor example does not work for me, just showing this line and then exit. Looking through the source code, it seems to be trying to locate runtime configuration with enviorment variable CORE_ROOT_64, CORE_ROOT_32(which is pretty unreliable?).
Can we inject a C++/CLI dll to the target process and let windows handle the runtime loading instead of manually locating it?