we are developing a test procedure using .net interop assemblies (as the customer prohibits direct use of LabVIEW VIs in his production area for some reason).
We have different hardware driver libraries based on the common low level drivers (AI/AO/DI - daqmx, PXI power supply - dcPower). All of those libraries are working just fine at the LabVIEW side.
The .net interop assembly creation out of the application builder works fine (but may be done on two different PCs). We have Teststand sandboxes for all of the libraries (separately!), which are working fine.
Now when we put the calls to libraries together, TestStand throws an exception, either at runtime or even when you create a new step (seems to relate to the modules already in memory)
An exception occurred inside the call to .NET member 'Autocalibration': System.TypeInitializationException: The type initializer for 'NI_PXI_4112.LvClient' threw an exception. ---> System.IO.FileNotFoundException: Missing Dependency in: Autocalibration.vi ---> NationalInstruments.LabVIEW.Interop.VIAssemblyException: Missing Dependency in: Autocalibration.vi --- End of inner exception stack trace --- at NationalInstruments.LabVIEW.Interop.LVRuntime.throwMissingDependencyException() at NationalInstruments.LabVIEW.Interop.LVRuntime.LVClientInit(ClientKind clientKind, IntPtr initRec) at NationalInstruments.LabVIEW.Interop.LVRuntime..ctor(String entryPointNames, String lvClientAssemblyPath, String lvRuntimeVersion) at NI_PXI_4112.LvClient..cctor() --- End of inner exception stack trace --- at NI_PXI_4112.NI_PXI_4112.Autocalibration(String resourceName, String channels, Int32& errCode, String& errSource)