With a package document, you can create a package or package installer to distribute applications to clients.
The following table helps you determine when to use a package or package installer.
||A single compressed file containing software intended for installation on a target machine.
||NI Package Manager or SystemLink
In most cases, you must add the package to a feed that also includes the dependencies of the package before installing.
|Add the package to a feed—clients of the software can subscribe to the feed and install the package from Package Manager via network access.
||A folder containing the main software package, package dependencies, and an executable file that extracts the package and installs it on a target machine.
By default, a package installer includes all of the package dependencies in the output so clients of the software can install the package without network access.
||Run the package installer file.
Reference package dependencies using feeds instead of including the dependencies in the output—when a package installer that references feeds runs, it retrieves dependencies from the feed locations.
Require installation of the exact hierarchy and versions of all the dependencies—when clients of the software install the package, the installer installs the exact versions of the dependencies found on the machine that built the package installer when it was built.
This is recommended only for installing on a clean machine because it might upgrade or downgrade installed packages on the target machine.