NI Package Management Idea Exchange

cancel
Showing results for 
Search instead for 
Did you mean: 

Install the same package to multiple versions of LabVIEW

We desperately need the ability to install the same package to multiple versions of LabVIEW. Specifically, we need support for symbolic paths as a destination (user.lib, vi.lib, instr.lib, etc). 

Basically duplicate the VI Package Manager's ability to install a package to multiple versions of LabVIEW. I think the VI Package Manager work flow should be duplicated as well.

 

FYI: 

https://labviewwiki.org/wiki/Package_Manager_Comparison

6 Comments
Member

Chris,

You may want to look into NI Package Builder (NIPB). NIPB does support more pre/post install/uninstall actions. It also has GUI and command line interface.

__________________________________
Bill Eisenhower
Certified LabVIEW & TestStand Developer
Member
Status changed to: Under Consideration
 
Member

Hey Chris,

 

I'd like to take a step back and ask a clarifying question to make sure I'm really understanding the problem we're trying to solve:

  1. Is it really that you want to be able to install the same package to multiple versions of LabVIEW? Or is it that the contents of a package (presumably some reusable piece of code) should be usable/accessible in more than one version of LabVIEW without modification?

More specifically,

  1. Is it that as a package author you don't want to have to rebuild or otherwise modify your package when a new version of LabVIEW is released?
  2. Is it that as a package consumer you don't want to have to wait for the author of a package to rebuild or otherwise modify their package when a new version of LabVIEW is released so that you can use it in the new version of LabVIEW?

Thanks.

 

Aaron Peña

Product Owner, Package and License Management

National Instruments

Active Participant

Hey Aaron

For sure. I think we have to define what "install" means.

When I say install I mean "all actions necessary to provide functionality and UI UX around a body of software". So that clearly entails the files that do the work like apis and such. But it also means palettes, wizards, and other IDE specifics such as install locations to vi.lib, user.lib, instr.lib and mass compiling, etc.

 

I would like to be able to have the same package provide the same user experience regardless of the version of LabVIEW they are using the software in. 

 

As the builder, I would like to build one package that accomplishes the installation as defined above. One of the most important reasons to have one package do the installation is to prevent confusion over what version of a package is installed.

 

As a user I don't want to have to grab the right package depending on my version of LabVIEW. Think of this as the NI-DAQmx model. I get DAQmx 19 and that installs "support" for LabVIEW 32 and 64 bit, 16, 17, 18 and 19. One "thing" does all that is necessary to provide the same user experience across the versions of LabVIEW found. 

 

And as a user, you're right... I don't want to wait for a new version of a package that provides support for a new version of LabVIEW. That would be dreadful and put a heavy burden on the developer of code. 

 

Hope that helps.

Active Participant

One slight amendment... I'd hope for the option to select one or multiple or all versions of LabVIEW found on the system. In other words, an installation doesn't force itself on all installed versions.

Member

That's very helpful. Thanks, Chris.

 

 - Aaron