04-14-2008 02:04 AM
04-14-2008 10:01 AM
04-15-2008 02:08 PM
Thanks a lot. Yes, the driver issue is clear.
Peter
06-25-2009 05:24 PM
Have to return to that message once again to clarify something in my mind. What exactly does "directly call into 64-bit code" mean? What will I be able to call from the 32-bit-TestStand on a 64-bit-machine?
I assume that calls into 32-bit DLLs, ActiveXs and .NET assemblies are fine. I guess that executable calls running 64-bit executables will also be OK. What about calls into 64-bit-compiled DLLs and .NET assemblies?
Regards
Peter
06-25-2009 06:30 PM
You will not be able to directly call 64-bit dlls and .NET assemblies that require being used as 64-bit (dotnet code can be set to use "Any CPU" so when called from 32-bit code it's 32-bit and 64-bit code it's 64-bit). You can call 64-bit COM servers (at least with TestStand 4.2) if they are external process exe servers or if you use a surrogate process if they are .dll servers.
Hope this helps,
-Doug
06-25-2009 06:59 PM
Yes, that helps a lot.
Thanks
Peter