I understand that eSignal only supports VB6 and VC++ 6.0 created DLLs to be used in conjunction with the EFS DLL Object. But I just upgraded from eSignal 7.9.1 to the new 10.0 release and wanted to let eSignal support something strange that's going on.
I can create unmanaged C++ DLLs with Visual Studio Express C++ 2005 and use them with eSignal 7.9.1 and everything works fine with the EFS DLL Object. However, this same DLL will not work with eSignal 10.0. The error message says that the EFS cannot load the DLL.
So, what I did next was to compile the C++ code with VC++ 6.0 and then have eSignal 10.0 try to load that with the EFS DLL Object. Now, everything works fine.
That's very strange that an older version of eSignal would be able to load a DLL that the latest version cannot. Just wanted to report this experience and, for anyone reading this, have they found the same kind of problem?
I can create unmanaged C++ DLLs with Visual Studio Express C++ 2005 and use them with eSignal 7.9.1 and everything works fine with the EFS DLL Object. However, this same DLL will not work with eSignal 10.0. The error message says that the EFS cannot load the DLL.
So, what I did next was to compile the C++ code with VC++ 6.0 and then have eSignal 10.0 try to load that with the EFS DLL Object. Now, everything works fine.
That's very strange that an older version of eSignal would be able to load a DLL that the latest version cannot. Just wanted to report this experience and, for anyone reading this, have they found the same kind of problem?
Comment