ExportVIStrings removed from LV 8.2?

[mjclarke]

We are using .Net to read values off a LabVIEW panel via COM - This is pretty straightforward.

In LabVIEW 7 we use the ExportVIStrings  COM command from .Net to dump the contents of the front panel to a text file and we  would get the control names from this file.

It appears that this command has been removed from the COM interface for LV 8 and not replaced (as far as i can see). I can resort to using the PrintVIToText command, but this is not at useful and would mean rewriting a fair-sized chunk of code.

Am I missing something or is there a better way to get a list of the front panel controls from another programming language (c#, vb, c++ etc).

Matt

[Wiebe@CARYA]

"mjclarke" <x@no.email> wrote in message news:1175254806676-499924@exchange.ni.com...
We are using .Net to read values off a LabVIEW panel via COM - This is pretty straightforward. In LabVIEW 7 we use the ExportVIStrings&nbsp; COM command from .Net to dump the contents of the front panel to a text file and we&nbsp; would get the control names from this file. It appears that this command has been removed from the COM interface for LV 8 and not replaced (as far as i can see). I can resort to using the PrintVIToText command, but this is not at useful and would mean rewriting a fair-sized chunk of code.Am I missing something or is there a better way to get a list of the front panel controls from another programming language (c#, vb, c++ etc).Matt


I'm not sure if it's exported or not, but the position of the ExportVIStrings has changed.


It's now under "VI Strings>Export", in stead of "ExportVIStrings". Perhaps you'll see it as "VI Strings.Export".


Hope it helps.


Wiebe.

[mjclarke]

Thanks for the reply.

Unfortunately, VI Strings does not show up through the COM interface either.

Matt

[Tom.]

Hello Matt,

I have taken a look at this issue and I experience the same behaviour. This has been escalated to our Research & Development team who will deal with the problem. As soon as there is any information available regarding this I shall post it on this forum to let yourself and anybody else with the same or similar issue know what National Instruments recommends as a course of action.

Let it be known that this is only experienced in LabVIEW 8 & 8.2, and selecting the LabVIEW 8.2 Type Library as an Automation reference within LabVIEW 7.0 / 7.1 doesn't display the same behaviour.

The help file for the VI Method (ActiveX) in LabVIEW 8.2 can be found online here for future reference.

Tom
NIUK