NI Package Builder 20.6 Bug Fixes

Overview

The following items are notable issues fixed between the release of NI Package Builder 20.5 and NI Package Builder 20.6, 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

1045471

Sequence File Included in Built Package Will not Execute if Override Packed Project Library step is Configured to Build PPL to a Higher Directory

Deploying a TestStand sequence file that contains a LabVIEW Packed Project Library (PPL) Override step with a LabVIEW project that builds the PPL to a directory above the sequence file results in a step that cannot execute. 

Workaround:

Configure the step to build the PPL in the directory of the sequence file, or rebuild the Override PPL after deploying the sequence file.

Reported Version:

NI Package Builder 20.0

Resolved Version:

NI Package Builder 20.6

Added:

Aug 19, 2020

1036386

Package Builder Appears Unresponsive when About Dialog is Hidden Behind Application

NI Package Builder appears unresponsive when the About dialog is hidden behind the Package Builder application when you click on the Package Builder in the taskbar before dismissing the About dialog.

Workaround:

Launch Windows Explorer and then immediately close it

Reported Version:

NI Package Builder 20.0

Resolved Version:

NI Package Builder 20.6

Added:

Aug 19, 2020

1035363

Rerunning Discovery After Building a Previously Missing Packed Project Library Still Results in Warning 16086

Adding a TestStand 2019 sequence file with a step that specifies a Packed Project Library (PPL) Override with a calling context project and the PPL is missing on disk will result in Warning 16086 "Discovery could not find the following dependency on disk". Rebuilding the PPL and rerunning discovery will still result in this warning another time even though the PPL is now on disk.

This issue is fixed in TestStand 2020.

Workaround:

Perform discovery a third time for Package Builder to properly locate the PPL.

Reported Version:

NI Package Builder 20.0

Resolved Version:

NI Package Builder 20.6

Added:

Aug 19, 2020

1035159

Package Builder Cannot Use TestStand after Build Fails Including an Override Packed Project Library that is Incompatible with the Active LabVIEW Version

Building a package causes the TestStand integration to no longer work after a build errors during staging when an included Override Packed Project Library (PPL) for a sequence step is incompatible with the active version of LabVIEW, such as a 64-bit PPL and 32-bit LabVIEW.

With Package Builder 20.6 and later, a restart is no longer required, but you must still disable the "process during staging" property for the file in the package for a successful build.

Workaround:

Restart Package Builder, and disable the "process during staging" property for the file in the package.

Reported Version:

NI Package Builder 20.0

Resolved Version:

NI Package Builder 20.6

Added:

Aug 19, 2020

1096778

Shortcut files (*.lnk) Cannot be Added to the Input Pane Using the Add File Dialog

Shortcut files (.lnk) cannot be added to the input pane using the Add File dialog, this will instead add the shortcut's target file.

Workaround:

Add the shortcut file by dragging the file from file explorer and dropping in the input pane or adding it as an item within a discoverable directory.

Reported Version:

NI Package Builder 19.0

Resolved Version:

NI Package Builder 20.6

Added:

Nov 14, 2020

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).