Reflector says that NHC.exe is a managed assembly and contains classes that provide ACPI.FIELD.Write() and ACPI.FIELD.Read() and soon. NHC's author described in the chm file how to create custom classes that include calls to these things for certain types of hardware, something like a plugin model.
Instead of dropping the .DLL, you are throwing the actual C # code into a special folder; obviously, nhc.exe dynamically compiles and runs this code when nhc.exe starts. If all this is true, you should write your own application that uses ACPI.FIELD.Read and Write calls, ACPI.FIELD.Read it into exe, specifying nhc.exe as a reference.
Although a kicker, it is that nhc.exe is confusing and all of these classes are not visible. Therefore, you cannot just run csc.exe and the nhc.exe link. I do not know for sure, but it seems to me that only this code can be run in the context of nhc.exe, which performs special compilation to process it.
Another bad news is that NHC development seems to have stopped; The forum site is dead, and the latest update is from 2007.
Cheeso
source share