Be able to have "custom action" VI with sub VI

olivier-jourdan 13 years ago updated by Michael Aivaliotis (VIPM Product Manager) 12 years ago 2
As far as I've seen "custom action" VI cannot have SubVIs. It might be useful to allow that.
One of my use case is to create a package to "install" QuickDrop shortcut in LabVIEW.ini file. Source code could be too large for manage user interface dedicated. Workaround I've used is not satisfying.
I should understand that my use case is perhaps  a wrong usage of VIPM. 

I proposed this idea in this JKI thread. I would like to see this.
One correction I'd like to make is that you can have subVIs in custom actions if the VIs you are calling ship with the LabVIEW version you are targeting. You could make a dynamic call to a subVI from the custom action that is installed at the target location which can contain SubVIs. Then you can delete the dynamic VI and subVIs. Another option is to create a LabVIEW executable that does the work you describe and then call that exe from a custom action VI.

I suggest that you create a separate idea request for the ability to modify ini files during package install\uninstall. Similer to modifying registry entries.