[2020 not a valid LabVersion for applying vipc file?]

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

[Shell Menu "Add Contents to VIPM Library" on .vip files]

On 7/23/2020 at 11:45 AM, StefanLemmens said:

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 the library without installing it in the free version anymore. I like to have (all) packages added to the library and then apply a small vipc to switch between different projects.

@Jim Kring Any thoughts or news about this?

[Shell Menu "Add Contents to VIPM Library" on .vip files]

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 the library without installing it in the free version anymore. I like to have (all) packages added to the library and then apply a small vipc to switch between different projects.

[Shell Menu "Add Contents to VIPM Library" on .vip files]

Is this going to be in the next VIPM version?

[Shell Menu "Add Contents to VIPM Library" on .vip files]

 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.

[Shell Menu "Add Contents to VIPM Library" doesn't work.]

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

[Shell Menu "Add Contents to VIPM Library" doesn't work.]

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 known command and stops reporting this error.

 

[Shell Menu "Add Contents to VIPM Library" doesn't work.]

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 :

Quote

 

=========== START of VIPM 2018.0.0 (build 2027) Error Message ===========
An internal VIPM 2018.0.0 (build 2027) Error has occured on: Tuesday January 14, 2020 at 03:44:30 PM

= Automated Message Start = 
Error 1 occurred at  [Launch File]:command (Unknown Enum Value <add>) Set Enum String 
Value__ogtk.vi in Read Key (Variant)__ogtk.vi:160002->Read Section 
Cluster__ogtk.vi->343FBFE9D2AE778BDCE948E13EDD148A->A37D44BD2FCED7810A2AC814B145247C->41AC743D0ED402
FF42A432FD77E580E0->VIPM Main Window.vi
Possible reason(s):
LabVIEW:  An input parameter is invalid. For example if the input is a path, the path might contain 
a character not allowed by the OS such as ? or @.
= Automated Message End =

= Error Handler Call Chain Start =
    VIPM Main Window.vi->
    41AC743D0ED402FF42A432FD77E580E0
= Error Handler Call Chain End =
=========== END of VIPM 2018.0.0 (build 2027) Error Message ===========

 

It looks as if the add-command is not supported (anymore)???

Best Regards,

Stefan