Skip to Content
0

Searching possibility to analyze initialization of OpenScan interface of WPF client

Feb 15, 2017 at 02:35 PM

41

avatar image

Hi experts,

Agentry Client: WPF Version 70.13.x
OS: Win 7 64bit Enterprise (DE)
.Net-Version: 4.6.01586


I have implemented the OpenScan interface for the Agentry WPF client, created a DLL and copied it into the "AlternateInput" directory.
On my local PC this is working as expected. The DLL is loaded by the Agentry client and executed.
On a customers PC this is not working; it is exactly the same configuration, same OS, etc. The AgentryClient is not showing any error, but the DLL is not being loaded.

My question is now:
Is there any possibility to let the client write a log or to debug it?

Regards,
Christian

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

2 Answers

Bill Froelich
Feb 15, 2017 at 06:34 PM
0

My first guess is that your DLL has a dependency that is not installed on your clients PC. I would check if you are missing a MSVC runtime used by your DLL or possibly something related to the SDK you are using in the DLL.

You can have your DLL popup a message box on initialization that displays a message with key details.

--Bill

Share
10 |10000 characters needed characters left characters exceeded
Christian Janson Feb 16, 2017 at 05:40 PM
0

Hi Bill,

thanks for your answer.

I had also tested with a DLL that was reduced to a absolute minimum: Only Interface implementation and a popup to show that the DLL was started; no dependencies at all (besides the AgentryClientSDK and the .Net-Framework itself).

But you have given me an idea: I will check with the sysinternals process monitor if I will find a hint to a DLL not being loaded.

Regards,

Christian

Share
10 |10000 characters needed characters left characters exceeded