Jim Kring

Hi @felipefoz (and @ShaunR). Thanks for posting this. Would you be willing to test to see if this is resolved in VIPM 2023 Q3 (build 2513 or later)? Details and download here:

Hi All, There is a VIPM 20203 release candidate available here: vipm-2023Q3-rc2-windows Some of the Fixes and Improvements: - VIPM now works with any LabVIEW Runtime greater than or equal to 20.1, to simplify installation process and avoid installing older versions of LabVIEW runtime if a newer version is installed (VIPM previously required exactly version 20.1 of the LV Runtime) - Fix Issue #25 affecting various user input dialogs (e.g. palette item renaming caused the dialog to get stuck and not close) - Improved package building in LabVIEW 2017-2019 (some improvements make for packages saved in LV 2020 and greater were back-propagated to work with older LabVIEW versions) - Speed-up of VIPM startup time for first launch after installation (installer now includes a cache of package info of latest versions of public packages) Please let us know if you run into any issues.

@rohit verma I believe that this has been fully removed. Our web/dev team has also added some automation to make this easier in the future. Thanks for your patience.

Sure, did you want the entire package removed, or just the one version that was published?

@Marco Pignati VIPM has a couple different checks for packages integrity. If one has significant concerns, it's possible to serve your own repository of trusted packages with a VIPM Pro team repository.

@Youssef Menjour The HAIBAL package was published on the NI Tools Network and VIPM is showing that, since NI has integrated it with VIPM. Was your package removed from the LabVIEW Tools Network repository?

Hi @Hameed Ibrahim. Does the problem resolve if you upgrade to VIPM 2023?

This gets my vote

I think I know what's going on here... Overview of the Problem The package's pre/post install/uninstall custom actions didn't know about a versioning convention change in LabVIEW 2022 Q3 (see the "More Details..." section below). The Error 7 is because the package's install action is looking in the wrong folder (the "22.3" folder doesn't exist -- it should be using the "22.0" folder). Wrong Folder Location (that package install action is using): C:\Program Files\National Instruments\Shared\Example Finder\1.0\Products\LabVIEW\22.3 Correct Folder Location: C:\Program Files\National Instruments\Shared\Example Finder\1.0\Products\LabVIEW\22.0 More Details on the Versioning Convention Change Starting LabVIEW 2022, LabVIEW uses a YEAR and QUARTER versioning scheme (e.g. 22.3 -> 2022 Q3), however any folders on disk should assume that the decimal digit is zero. For example, in LabVIEW 2023 Q1 and LabVIEW 2023 Q3 (probably going to be released in the future....) the folder names should use "23.0" instead of "23.1" or "23.3". I'll ping NI and see what's the best fix.

Hi @Youssef Menjour It looks like it could be a file permission issue. The TPLAT installer requires running both VIPM and LabVIEW as Administrator. Can you try exiting VIPM and LabVIEW and then run both as Administrator, then retry installing TPLAT? -Jim

Sorry about that. There was a network issue that has been resolved. Can you please try again and let us know if it's working now for you? Thank you.

Hi Benjamin, We've updated the package's homepage on vipm.io with the new name. Note: - this change probably will not propagate to the VIPM Desktop client when searching for packages (until you change the display name in a new build of the package) - we hope to give publishers the ability to edit this for themselves in the future Regards, -Jim

If you could generate a LF and keys for testing, we could give it a try. Feel free to PM me if you prefer to share those privately.

Thanks for testing and the feedback.

Hi Youssef, If you have the TPLAT installed can you see if you're able to deactivate your add-on using the VI-based API? Perhaps one of the parameters is not correct. My initial thought is to try removing the XML tags ("<RSAKeyValue>" etc) and only use the key ("3JuX...") Otherwise, I'm not sure how to begin debugging that error message. -Jim

I also now see your point about context. A label such as "Library (.lvlib) file to bind with license (located in your source)" only makes sense if you're binding the license at build time. If you have already bound the library to a license then the label should be something like "Library (.lvlib) file that is already bound to license (located in your source)" We'll need to think more about the best way to fix this so that it makes sense for users.

I see your point about having a tick/checkbox to enable licensing & activation. FYI, I think that the the package builder supports building packages with lvlib's that are already bound to a license file -- you then have to uncheck the tick for "Bind license to library at build time (Recommended)"

@Youssef Menjour, I agree with you that this control should be renamed to something like: "Library (.lvlib) file to bind with license (located in your source)" Any thoughts on that name?

Yes, that's how it's supposed to work.

I think the problem is that your librairie.lvlib already is bound to the license file. When you build your package, VIPM will do the license binding for you. Try removing licensing from the lvlib and then build the package with VIPM.

We'll take a look. Thanks for posting a test/example.

@TomMcQ, @Joerg Hampel, @Youssef Menjour. We are testing a possible fix. Let's discuss offline if you want to help test before its released.

I sent you a message offline about how we can test a possible fix. Thanks.

Hi @Youssef Menjour. Thanks for posting such a detailed error report and including a sample project to reproduce the issue. There is a bug report in our public issue tracker, here: https://github.com/vipm-io/vipm-desktop-issues/issues/16 Thanks for your patience and the great suggestions.

VIPM 2023 RC1(release candidate 1) for Windows is now available for download! Please test and let us know if you have any issues, and reply to this forum post with any issues you find. Thanks for supporting a high quality release! >> Download Here << And, see the VIPM 2023.1 Release Notes for details about what's new.