NI Package Builder 20.5 Bug Fixes

Überblick

The following items are notable issues fixed between the release of NI Package Builder 20.1 and NI Package Builder 20.5, including additional patches and service packs. If you have an issue ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of NI Package Builder.

Bug Number

Legacy ID

Description

Details

135941

Misleading Error -19024 Occurs When Building Packages That includes a TestStand Sequence File that Calls a LabVIEW Project That is Missing Files

Building a TestStand sequence that calls a LabVIEW project that has any missing items will give "Error -19024 The following projects are open in the LabVIEW development system. Close all projects before creating a deployment." even though the LabVIEW project is not open. This issue is fixed by TestStand 2020.

Workaround:

Ensure that any LabVIEW projects called by TestStand sequence files have all of their items and files.

Reported Version:

NI Package Builder 19.0

Resolved Version:

NI Package Builder 20.5

Added:

Nov 18, 2019

135935

Unhelpful Error When Including a Broken VI and the 'Remove block diagrams' Option is Enabled

If you include a broken VI in a package and disable "Check for broken VIs" and enable "Remove block diagrams", NI Package Builder reports the below unhelpful error: "LabVIEW cannot compile one or more VIs because they do not have block diagrams. A VI broke during the build process from being saved without a block diagram. Either open the build specification to include the block diagram of that VI or enable debugging to include the block diagrams of all VIs in the build." This issue is fixed in TestStand 2020.

Workaround:

Ensure that all VIs in your Solution are not broken

Reported Version:

NI Package Builder 19.0

Resolved Version:

NI Package Builder 20.5

Added:

Nov 21, 2019

135941

When Building a LabVIEW Project with Missing Files, NI Package Builder Fails with Error -19024, Incorrectly Reporting the Project is Open in LabVIEW

If TestStand references a LabVIEW project that has missing files, then building a solution that contains that TestStand sequence file results in the following error: "Error -19024: The following projects are open in the LabVIEW development system. Close all projects before creating a deployment." This issue is fixed in TestStand 2020.

Workaround:

Fix the paths of all files in the LabVIEW project.

Reported Version:

NI Package Builder 19.0

Resolved Version:

NI Package Builder 20.5

Added:

Nov 21, 2019

985899

Building Solution Containing a Local Repository with Missing Properties Reports Vague Error -16022

Using Build Solution to build a local repository with missing properties such as an empty output directory will give "Error -16022 An error occurred while cleaning the output directory. 'Value cannot be null. Parameter name: path2'." without specifying which parameter is causing the error.

Workaround:

Ensure that all of the required Properties for the repository are complete.

Reported Version:

NI Package Builder 19.6

Resolved Version:

NI Package Builder 20.5

Added:

Mar 31, 2020

1047801

Renaming a Directory that Contains Hundreds of Files Causes Slowdown

Package Builder appears to hang when entering each character for a rename of a directory in the Editor Pane if the directory contains hundreds of files.

Workaround:

Temporarily move the files to a different directory location in the package, rename the directory, and move the files back to the renamed directory.

Reported Version:

NI Package Builder 20.0

Resolved Version:

NI Package Builder 20.5

Added:

N/A

1108853

Building a Local Repository Doesn't Copy EULA Packages

Package Builder does not include dependent NXG defined End User License Agreement (EULA) packages in a local repository.

Workaround:

Manually add the EULA to the local repository and use the "nipkg feed-add-pkg" command to update the feed to include the EULA. You can also building a package installer which will properly include the EULA package.

Reported Version:

NI Package Builder 19.6

Resolved Version:

NI Package Builder 20.5

Added:

N/A

1105686

Version is Empty for a Solution Package Without a Display Version in the Add Dependencies Dialog

The Add Dependencies dialog does not show the Version of a package in the Solution Packages tab if the solution package does not specify a display version.

Workaround:

There is currently no known workaround for this issue.

Reported Version:

NI Package Builder 20.0

Resolved Version:

NI Package Builder 20.5

Added:

N/A

Additional Patch Information

Installing some patches may require certain additional steps or considerations. Please refer to the following table for more information about patches for this release.

These patches currently do not have any special instructions.

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).