source distribution overwrite vi

[D60]

Hi!

I'm making a source distribution for my dynamically called VI's. These VIs operates on classes. I would like make one Distribution, that contains all called vis. My problem is, I've serveral overwrite class methods, with equal names as well. But when I make a preview, the distribution separates these vis, because they have similar names.

What is the common trick or solution for this problem?

Thanks in advance!

[D60]

Let me explain a little bit more. I've a top level VI, creates and manage LVClasses. All of my plugin VI's are dynamically called, and the lvClass parameter is set to the plugin vi by VI_Prop.Set_Control_Value. After I made some modification with my parameter object, this param. is returned to the top level vi.

Of course the top level VI is loaded at first, and the plugin is called by the user. Do I have to include the parameter class in my source distribution, dispite of the fact that, the class is created in the top level vi, so the class methods should be in memory by default. 

Thanks in advance!

I've attached a picture. Should this control be a valid object?

[Jiri_K · Accepted solution]

Hi Durnek,

1) dynamically loaded classes has to be added to always included section of build specification.

Add the classes as “Always Included” in the Source Files page of the Executable Properties dialog box

Place those classes into a directory next to the executable so that the relative path is still accurate. Follow these steps migrate the files along with the executable:

• Create new destination folders in the Destinations page of the Executable Properties dialog. These destination folders must have the same relative path to the executable as the source class did to the top-level VI.
• Navigate to the Source File Settings page of the Executable Properties dialog.
• Browse through the Project Files tree and modify the Destination settings so that each file is migrated to the appropriate destination directory.

Another solution is to add unused object anywhere to block diagram. Application builder will find the class then.

2) In the Additional Exclusions page of the Executable Properties dialog, remove the checkmark from the Modify project library file after removing unused members checkbox.

3) VIs with the same name inside executable are supported from LV 2009+, so the new layout has to be selected. Otherwise you will have to create separate llb or folder for each class. 

 

If you want to discuss more I would need to see your structure of the files. So you can either upload it in the forum or send it techsupport@ni.com. You can put my name into subject.

Regards,

Jiri Keprt

NI EE Czech Republic

[D60]

Thank you very very much!