NI Package Management Idea Exchange

Post an idea

This probably applies more to building a NI Package via Application Builder, but would be helpful if you could do it with NI Package Builder (NIPB). It should be easier to call a VI(s) as a custom execute steps of a package. You can do this currently by making your VI follow the LabVIEW CLI pattern. However this does requiring a lot of manual entry from the user to do in NIPB, thus being error prone. Also to do with the Application Builder, you have to make a batch file and add that to project even thought the batch fill does not need to exist other than to do the install/uninstall.

View All (3)

Cosmetic / Minor issue

I have a solution with one underscore character in its file name. It is properly displayed in the window title bar, but undescore is missing in most recently used files, under File menu.

I made some complementary tests, with dummy solution files named Undescore_One.pbs, Undescore_One_Two.pbs and Undescore_One_Two_Three.pbs. Only the first underscore in the file name is missing in menu display:

I am using NI Package Builder 20.6.0.1227.

Regards,

You can add folders to the "inputs" in NIPB, and they will auto detect if files have been changed / added to the solution.

If you ad a folder (or a complex folder hierarchy) to a package, it disconnects ALL of the folders. I completely understand why this might be done, but it creates a slightly unexpected disconnect between the "inputs" and the "package workspace"

If files are updated, those updates propagate between both locations -- Great!

If files are added, those updates propagate to the Inputs, but NOT the workspace.

This can be pretty frustrating, especially for deeply nested folder structures...

My request is not that this is entirely switched, but rather an option to add a linked folder to the workspace... My thought is that this would function much like the "autopopulating folders" from labVIEW (vs snapshots) -- Though it would be nice if the base added folder could have it's name changed and still maintain the link (though not required).

NI Package Management Idea Exchange

NI Package Management Idea Exchange

Add ability to call a VI as Custom Execute

Add ability to customize Custom Execute text

NI Package Builder - Improve MRU file name display (first underscore is missing)

NIPB: Add option to Add File without Discovery

NI Package Builder - Add Ability to Link Folders to Package