Does anyone know how to package the Command expert drivers so the VB application runs as a standalone application? VB.net creates all dependencies so all dll files and COM objects instantiated are brought into the installer to create the installer (i.e., setup.exe and Installer.msi files).
Turns out when I install the created installer from VB.net 2010 into another fresh pc that does not have IO libraries and command expert, the Packaged application will not run!
I was under the impression that once I package the DLL file Ag3497x_1_13.dll, Agilent.CommandExpert.Common.dll, Agilent.commandexpert.InstrumentAbstraction.dll, Agilent.CommandExpert.Scpi.dll, AgSCPI99_1_0.dll, and IVI.Visa.Interop.dll, the application could run on any PC without depending on Command expert suite, or IO libraries suite. Clearly I am either doing something wrong, or I am not including the correct items.
In the computer that does not have CE, and IO Libs, I get a similar message to this message. I didn't copy the error since I got it on another PC. I googled the error and it has to do with the drivers not being able to be registered by regsvr32.
Retrieving the COM class factory for component with CLSID {000209FF-0000-0000-C000-000000000046} failed due to the following error: 80040154
The visual Basic 2010 installer generates a warning which makes me think something is wrong with my setup or the driver itself. The funny thing is that I can't tell if I always got the error because in debug mode as I am developing the code, I never saw this error. It is likely that I never saw any errors because VB.net is talking to Command expert and other drives, and IO libraries which are installed in my development PC. Maybe I have everything it needs to run, unlike the pc which does not have CE and IO Libs. My code will not run!
WARNING: Unable to find dependency 'IVI.VISA.INTEROP' (Signature='A128C98F1D7717C1' Version='3.0.0.0') of assembly 'Agilent.CommandExpert.Scpi.dll'
The other PC does not have CE and IO libs, so my code won't run in that pc.
I am sure someone at Agilent ran into this very same issue, and perhaps someone at Agilent tell me what additional files I need to add to the installer, VB.net commands to include so the installer executes during the installation if any, path location where additional files need to go (i.e., system32 etc...), and any batch files (*.bat) and how to load them into vb for the installer for it to run it all from my generated setup.exe?
I don't believe I have all the necessary files to make my program run identically to my development machine. I seriously doubt the answer will be to install Command Expert and IO libs in order for my application in any machine! That is not the case in LabView for sure.
I am attaching a picture of the VB.net Installer, and all the dependencies files it brought in automatically. Also the warning I am getting. I believe there are more files that need to be installed in different locations for this work. I just don't know what that is.
Creating an installer with just those DLL files, it does not work!
Help please!
Edited by: rjrodrig on Apr 28, 2012 5:51 PM