StefanLemmens

Is the new VIPM API package available? Has this been fixed already?

@Jim Kring Any thoughts or news about this?

I had tested it in the Community version of VIPM and that works very well. But now I notice that it doesn't work in the Free version. It gives a dialog that says "This feature of the VIPM API does not function with the Free version of VIPM." Is this intended or a bug? Because I would expect that a shell menu just works no mather which version I installed (or that it wouldn't be available if I can't use it). In VIPM 2019 I could "Add Contents to VIPM Library" for a vipc file in the free version but in 2020.1 this also gives this pop-up. So it looks like there is no way to add a package to

Is this going to be in the next VIPM version?

It would also be nice to have the shell menu option "Add to VIPM Library." on *.vip files and not only on *.vipc files. This way *.vip files can be added to the VIPM library from the windows explorer without having to install them.

Thanks. It would also be nice to have the "Add to VIPM Library." option on *.vip files and not only on *.vipc files.

It also looks like VIPM keeps on trying to execute this unknown command because I noticed that the error logfile keeps on growing every 100ms until I close the VI Package Manager. The error logfile than contains this error message about 10 times per second. Even restarting the VIPM doesn't stop the error logfile from growing. It just keeps adding the same message over and over. Even restarting the PC doesn't seem to help. Whenever VIPM is open the error logfile keeps on growing. It only stops when I select "Apply Configuration" in the context menu because then VIPM can execute a

When I right-click on a vipc file in the windows explorer the context menu shows the option "Add Contents to VIPM Library". Selecting this opens the VI Package Manager but the contents of the vipc file are not added to the VIPM Library. The vipc file definitely contains the vip itself. The error file (located at C:\ProgramData\JKI\VIPM\error) contains the following error : It looks as if the add-command is not supported (anymore)??? Best Regards, Stefan