LabVIEW Wiki - User contributions [en]

NI Package Manager

2025-01-08T08:31:34Z

Oli wachno:

The NI Package Manager (https://www.ni.com/en/support/downloads/ni-package-manager.html) is NI's proprietary version of a Debian package manager software framework.
Almost every NI Software is installed using NI Packages (*.nipkg).
A very handy feature is the possibility to define package dependencies incl. version numbers.

== Consuming NI Packages ==

The mostly known way of consuming *.nipkg files is the NI Package Manager GUI (%Programs%\National Instruments\NI Package Manager\NIPackageManager.exe on Windows machines). NI Package Manager GUI is registered as the default application for handling *.nipkg files during installation.

The GUI is an application providing easier access to the usage of the Package Manager. Generally speaking it is a Windows application wrapping the functionality of the underlying command line tool (%Programs%\National Instruments\NI Package Manager\nipkg.exe on Windows machines) and providing a kind of shop experience for the user.

'''INFO:'''
since NI Package Manager is used to install software to the computer, it requires administrative privileges to run.

== Use Cases for uisng NI Packages ==
* Installation of NI Software (like LabVIEW, TestStand, ....) and required components
* TestStand Deployments
* Installation of general software packages incl. required dependencies

== Contents of NI Packages ==
A NI Package can consist of different contents depending on what kind of software needs to be distributed

* Distribution and execution of MSI installers
* Distribution of files and folder structures
* Distribution of multiple nipkg files (Package of Packages)

== Internal structure of an NI Package ==
An *.nipkg file is an archive file which holds a defined file / folder structure. Detailed information can be found at https://www.ni.com/docs/en-US/bundle/package-manager/page/package-components.html

== How to create *.nipkg files ==
There are different possibilities to create nipkg files; the choice which one to actiually use is dependant on your workflow.

=== Using LabVIEW Build script ===
Details to be added

=== Using TestStand Deployment Tool ===
Details to be added

=== NI Package Builder ===
[[NI Package Builder]]

=== nipkg.exe ===
Refer to https://github.com/mbilyk/NIPM-Tutorial/blob/master/README.md for details

[[Category:NI Package Manager]]

NI Package Manager

2025-01-07T13:54:44Z

Oli wachno: /* NI Package Builder */

The NI Package Manager (https://www.ni.com/en/support/downloads/ni-package-manager.html) is NI's proprietary version of a Debian package manager software framework.
Almost every NI Software is installed using NI Packages (*.nipkg).
A very handy feature is the possibility to define package dependencies incl. version numbers.

== Consuming NI Packages ==

The mostly known way of consuming *.nipkg files is the NI Package Manager GUI (%Programs%\National Instruments\NI Package Manager\NIPackageManager.exe on Windows machines). NI Package Manager GUI is registered as the default application for handling *.nipkg files during installation.

The GUI is an application providing easier access to the usage of the Package Manager. Generally speaking it is a Windows application wrapping the functionality of the underlying command line tool (%Programs%\National Instruments\NI Package Manager\nipkg.exe on Windows machines) and providing a kind of shop experience for the user.

'''INFO:'''
since NI Package Manager is used to install software to the computer, it requires administrative privileges to run.

== Use Cases for uisng NI Packages ==
* Installation of NI Software (like LabVIEW, TestStand, ....) and required components
* TestStand Deployments
* Installation of general software packages incl. required dependencies

== Contents of NI Packages ==
A NI Package can consist of different contents depending on what kind of software needs to be distributed

* Distribution and execution of MSI installers
* Distribution of files and folder structures
* Distirbution of multiple nipkg files (Package of Packages)

=== Internal structure of an NI Package ===
An *.nipkg file is an archive file which holds a defined file / folder structure. Detailed information can be found at https://www.ni.com/docs/en-US/bundle/package-manager/page/package-components.html

== How to create nipkg files ==
There are different possibilities to create nipkg files; the choice which one to actiually use is dependant on your workflow.

=== Using LabVIEW Build script ===
Details to be added

=== Using TestStand Deployment Tool ===
Details to be added

=== NI Package Builder ===
[[NI Package Builder]]

=== nipkg.exe ===
Refer to https://github.com/mbilyk/NIPM-Tutorial/blob/master/README.md for details

NI Package Builder

2025-01-07T13:53:18Z

Oli wachno: Created page with "The NI Package Builder is another tool on top of NI Package Manager providing easier accessibilty to creating nipkg files (and compiling feed contents). It is worth noting that there is a 32- and a 64 bit version. Difference in bitness has subtle effects on the output files. The following descriptions are bitness-agnostic, differences between the versions will be pointed out seperately. == Solution files == NIPB uses so called solution files (*.pbs) to store configurat..."

The NI Package Builder is another tool on top of NI Package Manager providing easier accessibilty to creating nipkg files (and compiling feed contents).
It is worth noting that there is a 32- and a 64 bit version. Difference in bitness has subtle effects on the output files.

The following descriptions are bitness-agnostic, differences between the versions will be pointed out seperately.

== Solution files ==
NIPB uses so called solution files (*.pbs) to store configuration data for the package(s) to be build. Correctly used, they offer a productivity boost.
All following examples are use a .pbs file.

== Building a nipkg based on files to be copied to specific folders on the target ==

'''Prerequisites:''' nipkg payload exists as distributable files accessible from the machine, NIPB is running on.

* Locate the Packages pane on the top right of the NIPB UI. Add a new package using the appropriate button. Assign an appropriate name.
[[File:NIPB Package Pane New Package.png|center|frameless]]

* Note that on the bottom right part of the NIPB UI, the Property pane populates with the information of the item under focus. Fill in information in the Property pane as required

[[File:NIPB Package Pane Package Properties.png|center|frameless]]

* In the centre of the NIPB UI, a tab with a standard folder structure appears.

[[File:NIPB_Package_Folder_Pane.png|center|frameless]]

* Locate input pane on the left side of the NIPB UI. Use button to open the dialog.

[[File:NIPB Input Pane Add.png|center|frameless]]

* Add files / folders as needed using the Input pane on the left side of the NIPB UI

[[File:NIPB Input Pane Filled.png|center|frameles]]

* Assign source files to specific locations on target machine via Drag and Drop into the folder structure of the package. The available folders are the so called Target Root Directories (Reference to https://www.ni.com/docs/en-US/bundle/ni-package-builder/page/targetrootdirectories.html). Note that depending on the bitness setting of your package, you will only have [Program Files (32Bit)] available.

[[File:NIPB Package Assignment Standard.png|center|frameless]]

* If you need your files to go in a different location than the Target Root Directories, you can add a custom sub folder structure. Please also note the following section Target Folder Considerations (to be added)

[[File:NIPB Package Assignment custom dir.png|frameless|center]]

* Upon having finished the file assignments, the package is ready to be build. Build can be initiated by using the application menu

[[File:NIPB Package Build via menu.png|frameless|center]]

the button on the packages pane

[[File:NIPB Package Build via button.png|frameless|center]]

or pressing ''Ctrl+F6''

If you haven't previuosly saved the active configuration, NIPM will kindly prompt you to do so.

=== Package build result ===
Browse to the build output directory for your packacge.

[[File:NIPB Browse build output.png|frameless|center]]

Note that the output diretory contains a nipkg file and a folder. The nipkg is just an archive file of the folder located alongside.

== Target folder considerations ==
To be added

File:NIPB Browse build output.png

2025-01-07T13:50:45Z

Oli wachno:

NIPB Browse to build output

File:NIPB Package Build via button.png

2025-01-07T13:48:41Z

Oli wachno:

NIPB Package Build via button

File:NIPB Package Build via menu.png

2025-01-07T13:47:56Z

Oli wachno:

NIPB Package Build via menu

File:NIPB Package Assignment custom dir.png

2025-01-07T13:46:49Z

Oli wachno:

NIPB Package Assignment custom dir example

File:NIPB Package Assignment Standard.png

2025-01-07T13:44:21Z

Oli wachno:

NIPB Package Assignment Standard Root Directories

File:NIPB Package Folder Pane.png

2025-01-07T13:39:02Z

Oli wachno:

NIPB Package Folder Pane

File:NIPB Package Pane Package Properties.png

2025-01-07T13:37:48Z

Oli wachno:

NIPB Package Pane Package Properties Pane

File:NIPB Package Pane New Package.png

2025-01-07T13:36:40Z

Oli wachno:

NIPB Package Pane New Package

File:NIPB Input Pane Filled.png

2025-01-07T13:33:30Z

Oli wachno:

NIPB Input Pane with information filled

File:NIPB Input Pane Add.png

2025-01-07T13:24:55Z

Oli wachno:

NI Package Manager

2025-01-07T13:14:10Z

Oli wachno:

The NI Package Manager (https://www.ni.com/en/support/downloads/ni-package-manager.html) is NI's proprietary version of a Debian package manager software framework.
Almost every NI Software is installed using NI Packages (*.nipkg).
A very handy feature is the possibility to define package dependencies incl. version numbers.

== Consuming NI Packages ==

The mostly known way of consuming *.nipkg files is the NI Package Manager GUI (%Programs%\National Instruments\NI Package Manager\NIPackageManager.exe on Windows machines). NI Package Manager GUI is registered as the default application for handling *.nipkg files during installation.

The GUI is an application providing easier access to the usage of the Package Manager. Generally speaking it is a Windows application wrapping the functionality of the underlying command line tool (%Programs%\National Instruments\NI Package Manager\nipkg.exe on Windows machines) and providing a kind of shop experience for the user.

'''INFO:'''
since NI Package Manager is used to install software to the computer, it requires administrative privileges to run.

== Use Cases for uisng NI Packages ==
* Installation of NI Software (like LabVIEW, TestStand, ....) and required components
* TestStand Deployments
* Installation of general software packages incl. required dependencies

== Contents of NI Packages ==
A NI Package can consist of different contents depending on what kind of software needs to be distributed

* Distribution and execution of MSI installers
* Distribution of files and folder structures
* Distirbution of multiple nipkg files (Package of Packages)

=== Internal structure of an NI Package ===
An *.nipkg file is an archive file which holds a defined file / folder structure. Detailed information can be found at https://www.ni.com/docs/en-US/bundle/package-manager/page/package-components.html

== How to create nipkg files ==
There are different possibilities to create nipkg files; the choice which one to actiually use is dependant on your workflow.

=== Using LabVIEW Build script ===
Details to be added

=== Using TestStand Deployment Tool ===
Details to be added

=== NI Package Builder ===

=== nipkg.exe ===
Refer to https://github.com/mbilyk/NIPM-Tutorial/blob/master/README.md for details

GLA Summit 2021/LV Solution Builder: The Missing Secret Sauce to Packed Project Libraries (PPLs)

2021-12-17T18:05:20Z

Oli wachno: /* Presentation Links */

''' LV Solution Builder: The Missing Secret Sauce to Packed Project Libraries (PPLs)''' by Karthik Abiram and Phil Joffrain

''Usually setting up a plugin-based architecture using Packed Project Libraries (PPLs) requires multiple steps and makes the source code difficult to debug and maintain. But using LV Solution Builder, you get to keep your source code open and simple like a normal LabVIEW project and still get all the benefits of Packed Project Libraries (PPLs) at the executable level.''

== Presentation Links ==
* [https://youtu.be/e2GGAuA_Ees?t=784 Presentation on YouTube]

== See Also ==

== External Links ==

[[Category:GLA Summit 2021]]

GLA Summit 2021/Beyond mere git - the powers of merge request

2021-12-17T18:03:05Z

Oli wachno:

'''Beyond mere git - the powers of merge request''' by Michal Radziwon

''It has became a standard among LabVIEW developers to use SCM solutions, among which, the git is one of the most popular. At the same time, many developers and teams decide to use self-hosted or cloud-integrated git repository managers like GitLab or GitHub which provide many more functionalities than git server. In this presentation I am going to show how to use a "merge request" to boost the performance in team-collaboration, code review process, and providing an enabler for incremental integration of CI/CD.''

== Presentation Links ==
* [https://youtu.be/e2GGAuA_Ees?t=332 Presentation on YouTube]

== See Also ==

== External Links ==

[[Category:GLA Summit 2021]]
[[Category:GIT]]

GLA Summit 2021/Beyond mere git - the powers of merge request

2021-12-17T18:02:28Z

Oli wachno:

'''Beyond mere git - the powers of merge request''' by Michal Radziwon

''It has became a standard among LabVIEW developers to use SCM solutions, among which, the git is one of the most popular. At the same time, many developers and teams decide to use self-hosted or cloud-integrated git repository managers like GitLab or GitHub which provide many more functionalities than git server. In this presentation I am going to show how to use a "merge request" to boost the performance in team-collaboration, code review process, and providing an enabler for incremental integration of CI/CD.''

<div style="text-align:center;"><youtube width="800" height="600">e2GGAuA_Ees?t=333</youtube></div>

== Presentation Links ==
* [https://youtu.be/e2GGAuA_Ees?t=332 Presentation on YouTube]

== See Also ==

== External Links ==

[[Category:GLA Summit 2021]]
[[Category:GIT]]

GLA Summit 2021/What's New In TestStand 2021

2021-12-17T17:59:53Z

Oli wachno:

'''What's New In TestStand 2021''' by Carlos Gonzalez

''We did an overhaul of the Sweep Loop step in TestStand 2021. Come and see the new capabilities that were introduced to streamline workflows with the Sweep Loop step.''

<div style="text-align:center;"><youtube width="800" height="600">e2GGAuA_Ees</youtube></div>

== Presentation Links ==
* [https://youtu.be/e2GGAuA_Ees Presentation on YouTube]

== See Also ==

== External Links ==

[[Category:GLA Summit 2021]]
[[Category:TestStand]]

GLA Summit 2021/Per-Project Package Installation and Configuration Management with VIPM and Dragon

2021-12-17T17:52:00Z

Oli wachno:

'''Per-Project Package Installation and Configuration Management with VIPM and Dragon''' by Jim Kring

''Per-Project Package Installation and Configuration Management with VIPM and Dragon''

<div style="text-align:center;"><youtube width="800" height="600">xwkzOsP51tM</youtube></div>

== Presentation Links ==
* [https://youtu.be/xwkzOsP51tM Presentation on YouTube]

== See Also ==

== External Links ==

[[Category:GLA Summit 2021]]
[[Category:JKI]]
[[Category:Package Manager]]
[[Category:Presentations]]
[[Category:Package Manager]]
[[Category:Presentations]]

GLA Summit 2021/Package Management

2021-12-17T17:49:20Z

Oli wachno:

'''Package Management'''

Panel discussion with:
* Adam Brown
* Niki Budgell
* Chris Cilino
* Kane Johnson
* Jim Kring
* Scott Richardson
* Wes Wendland

<div style="text-align:center;"><youtube width="800" height="600">gk7yxKdwuOw</youtube></div>

== Presentation Links ==
* [https://youtu.be/gk7yxKdwuOw Watch on Youtube]

== See Also ==

== External Links ==

[[Category:GLA Summit 2021]]
[[Category:Package Manager]]
[[Category:Panel Discussion]]
[[Category:Package Manager]]
[[Category:Panel Discussion]]

GLA Summit 2021/NI Package Manager: Past, Present and Future

2021-12-17T17:46:50Z

Oli wachno:

'''NI Package Manager: Past, Present and Future''' by Niki Budgell, Scott Richardson, and Wes Wendland

''This presentation will walk through NI’s installer technology and the role of NIPM. If you use NI software, there is a high likelihood that you have interacted with NIPM in some capacity, either through an installation or through building a deployment. This presentation will talk through some of the motivation behind why NIPM was created, what NIPM is used for today, and what direction NIPM and its installers are heading in the future. ''

<big>Don't forget to take part in the [https://forms.office.com/Pages/ResponsePage.aspx?id=mh-6h81EpkOwCG_bRaUgTvSsrWkvHSVEubfatZ7qGZFUNlpLUjI1OEpaMFRUWDlMWFBMSTI2VThMWS4u survey]</big>

<div style="text-align:center;"><youtube width="800" height="600">Jj4MxWIZ89s</youtube></div>

== Presentation Links ==
* [https://youtu.be/Jj4MxWIZ89s Presentation on Youtube]

== See Also ==

== External Links ==

[[Category:GLA Summit 2021]]
[[Category:Presentations]]
[[Category:NIPM]]
[[Category:Package Manager]]
[[Category:NIPM]]
[[Category:Package Manager]]

GLA Summit 2021/An in-depth look at Test Executives

2021-12-17T17:41:43Z

Oli wachno:

'''An in depth look at Test Executives''' by Sam Roundy

''Test executives are frameworks that help maximize code reuse as well as minimize the time it takes to write automated tests. Having the right test executive can save companies a lot of money. The question is: should you write one or buy one? What makes a good test executive? This presentation discusses these questions and much more related to test executives.''

<div style="text-align:center;"><youtube width="800" height="600">q9HMsenhRRc</youtube></div>

== Presentation Links ==
* [https://youtu.be/q9HMsenhRRc Presentation on Youtube]

== See Also ==

== External Links ==

[[Category:GLA Summit 2021]]
[[Category:Presentations]]

GLA Summit 2021/10 things to know (or more) about events in LabVIEW

2021-12-17T17:38:59Z

Oli wachno:

'''10 things to know (or more) about events in LabVIEW''' by Olivier Jourdan

''Events appear in LabVIEW 7.0, but they are still not appreciated as they deserve by lots of LabVIEW developers. In this presentation, we will speak about 10 things you should really know to get the best from this old LabVIEW feature.''

<div style="text-align:center;"><youtube width="800" height="600">ddXp1Itpq0M</youtube></div>

== Presentation Links ==
* [https://youtu.be/ddXp1Itpq0M Presenation on Youtube]

== See Also ==

== External Links ==

[[Category:Presentations]]
[[Category:GLA Summit 2021]]

GLA Summit 2021/10 things to know (or more) about events in LabVIEW

2021-12-17T17:34:21Z

Oli wachno: /* Presentation Links */

'''10 things to know (or more) about events in LabVIEW''' by Olivier Jourdan

''Events appear in LabVIEW 7.0, but they are still not appreciated as they deserve by lots of LabVIEW developers. In this presentation, we will speak about 10 things you should really know to get the best from this old LabVIEW feature.''

== Presentation Links ==
[https://youtu.be/ddXp1Itpq0M Presenation on Youtube]

[[Category:Presentations]]

== See Also ==

== External Links ==

[[Category:GLA Summit 2021]]