03-20-2021 11:03 AM - edited 03-20-2021 12:01 PM
NI Package manager is such garbage!
Why can't NI Package Manager simply NOT upgrade something if the installed version is >= to the version that it want's to install?
Blowing up because the installed version is the same is really really really bad programming. And always giving the same generic warning about my internet connection regardless of why it errors out is even worse.
03-21-2021 01:05 AM
Well, it does say it's a higher version (20.1 as opposed to 20.0), but I don't know why the build version is the same. That is usually always incrementing.
I don't have enough experience with NIPM myself to offer further opinions, but it certainly seems to be annoying many people.
03-21-2021 06:40 AM
@tst wrote:
I don't have enough experience with NIPM myself to offer further opinions, but it certainly seems to be annoying many people.
Yes, I'd guess it annoys almost anyone who installs LabVIEW. Since LabVIEW 2017 was released with NIPM as its "Installation Manager", I have probably run NIPM close to 100 times to get one or more post-2016 versions of LabVIEW installed on my (or my colleagues') computers. I would estimate that 80-90% of these installations have resulted in an NIPM "failure to install" (not dissimilar to a well-known "What we have here is a Failure to Communicate"), and maybe 30-40% involved a complete removal of all NI software from the PC before "trying again". I wish I could say "it is getting better", but LabVIEW 2020 SP1 is a striking counter-example to this faint hope ...
Bob Schor
03-21-2021 01:46 PM
03-21-2021 03:03 PM
@mcduff wrote:
Did you see this?
Um... Yeah, that error message advising me to "Please check your internet connection and try again" is NI's generic "We don't know what happened, so we are going to blame your internet connection" message.