NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Dll module path

Solved!
Go to solution

Hi Ppl

 

Is there any TestStand API to get the module paths of a DLL adapter type step. I was referring to the teststand help in the following link . But i was not able to locate the correct property. Similarly I also want to get the module paths of ActiveX, Dot Net adapter type steps. I had success in only getting the LabVIEW VI paths using LabVIEWModule.VIPath.

 

Thanks 

0 Kudos
Message 1 of 4
(4,344 Views)
Solution
Accepted by lordsathish

The module path is a hidden property, so searching for it without enabling "Show Hidden Properties" in the Station Options will make it a little difficult.

Each step has a hidden container called TS where step specific data is stored. The lookup string you are looking for is:

For CVI and C/C++ Adapter: Step.TS.SData.Call.LibPath

For .NET Adapter: Step.TS.SData.Call.AssemblyPath

 

 

hope this helps,

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
Message 2 of 4
(4,336 Views)

You can get the module paths for both DLL and CVI modules by using the CommonCModule API class:

 

dllModule.AsCommonCModule.ModulePath

 

For DotNet modules, you use the GetAssembly method. I don't think the ActiveX/COM module stores a path to the COM server. 

Message 3 of 4
(4,327 Views)

NOTE: Using the API that Erik mentioned is the preferred solution for accessing code module information. We will maintain backwards compatibility for the API whenever possible. Property locations, on the other hand, are more likely to change between versions of TestStand. Thus using the API is more future proof.

 

-Doug

Message Edited by dug9000 on 03-12-2010 01:12 PM
Message 4 of 4
(4,313 Views)