We are currently using the hardware driver DLL for the specific hardware with which we interact. However, we also have an old internally developed DLL, written with VC ++ around 2002, which wraps this DLL for several basic functions. This code has long been lost, and it was well designed before I went on stage. Therefore, it cannot be supported or even viewed in the event of a failure. We are trying to cut the middleman by accessing the driver directly from our C # .NET application.
I know this DLL just wraps the hardware vendor DLL, but the method signatures do not match. It looks like it calls several driver functions in one method. My question is this: how can I see all the external calls that the DLL shell makes in the DLL driver for this particular function? I am not interested in any other code; I am quite sure that I can deduce that if I can just find out what calls he makes to the driver.
Edit: a more concise explanation (what is compiled) ...
Driver.dll has a function StartAcquisition(int, string). It also has many customization features.
Wrapper.dll has a function StartAcquisition(int, string, double, int).
I suspect that the Wrapper.dll calls Driver.dll StartAcquisition(int, string)in addition to a few other calls (probably these configuration functions). I want to know what other challenges might be.
source
share