NI Package Management Idea Exchange

Post an idea

This may be a "bug" rather than a feature request.

But it seems as though when NIPM encounters an error in fetching information from one feed, it aborts checking all feeds...

I can see the benefit of this (if a computer is offline, it would prevent experiencing a time-out for 50+ feeds), but in some cases it becomes VERY difficult to install new software from feeds.

For instance:

- Computer is loaded with NI software online.

- Computer is installed at customer site, or into IT network, and is removed from outside communications

- New LAN feed is registered for "custom" software

NIPM will not see any of the custom software because it errors out on the public feeds. Work arounds are:

- Download and explicitly install packages

- Unregister ALL internet feeds (a non-obvious process, particularly for the NIPM feeds), reregister local feeds, try again.

It would be nice if there was some option I could enable that says "ignore errors and proceed with feed update"... or something.

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

think NI should allow the already stable and robust Update Service to download the latest packages/update and install them, while continue to fix/upgrade NIPM, Shouldn't put all eggs in the same basket. The current and recently updated NIPM is so frustrating that it can fail before initiating the download. the previous version kicked the bucket after hours into downloading, failing within inches from the finishing line. please consider not all users have fast and reliable internet connectivity.

NI Package Management Idea Exchange

NI Package Management Idea Exchange

Ignore Feed Error Loading

NI Package Builder - Add Ability to Link Folders to Package

NIPM: Add the ability to see non-patch Updates

NI Update Service to be concurrent with NIPM until NIPM is stable