02-02-2007 05:33 PM
02-04-2007 06:44 PM
You can acquire the IVI standard directory from the registry:
IviStandardRootDir variable (REG_SZ type) under HKEY_LOACL_MACHINE\SOFTWARE\IVI.
Every IVI driver binary (DLL) must be placed under the BIN subdirectory. Also, the BIN directory is added to the PATH environment variable by installing IVI Shared Components, therefore DLLs placed there can be implicitly loaded when you omit "full path" for LoadLibrary() call.
02-05-2007 08:51 AM
02-05-2007 11:12 AM
I appreciate your replies Makoto and z_haider. Yes this is for a COM dll - and no - the DLL is not necessarily going to be in the IVI\bin directory because during development it can be anywhere, but of course it is still registered by regsvr32 into the registry.
Looking at what's returned from the ConfigStore for the ProgID it's something like: "XComDriver.XComDriver".
I'd like to do this in C#, but I'll try your suggestions for CoCreateInstance and/or using IUknown* in C++ first.
If you had some example code that you could post which uses one of these methods and shows how to get to eventually get the IIviSwtch object - that would be great. Meanwhile I'll dig around to try and find an example myself.
Thanks again.
02-05-2007 11:52 AM
// YourClass yourInst = dcomObj as YourClass;
mySwtch.Initialize(strRes,
false, false, strOptions);04-15-2008 04:17 AM
How can I discover the ProgID using IVI-OCM??
Is the progIP common for a class driver??
i would to know it before??
Thanks
04-15-2008 06:51 AM
04-15-2008 07:43 PM
04-16-2008 03:06 AM
04-16-2008 04:05 AM - edited 04-16-2008 04:08 AM