[How to change a VI Package name]

Hi Everyone,

Does any of you had faced this kind of needs?

[How to change a VI Package name]

I've implemented a package with a very specific name (e.g "Error Dialog with Copy to Clipboard") but going through new needs I came with more general feature for this particular package. Now a better package name should be something like "Improved Error Dialog". I would like to know if it s possible to change the VI Package name displayed on VIPM (app or website) without changing the *.vip file?

[Unpublish Package]

Excellent.

Thanks a lot for your help.

[Unpublish Package]

You're correct the replacement package is the one you mentioned from Neosoft Technologies. 

[Unpublish Package]

Thanks Jim for your quick answer.

Could you please unpublish this package: https://www.vipm.io/package/benjaminr_lib_open_dqmh_request_handling_case/?

[Unpublish Package]

Hi everyone,

I was wondering if it is possible to unpublish a package? or redirect old published package to a new publisher one? 

Here is the situation: I've development a package published on my own name and my company want to put effort into open-source and centralizing internal individual effort under the company name. So, we just release a new package but on the company name and I would like to unpublish my first package or at least redirect to my company one. 

[Text cut on the VIPM - Working dialog during Extensions installation]

Text is cut on the VIPM - Working dialog displayed during the VIPM Extensions installation process. 

Running on a VirtualBox VM with Windows 10 x64 English with French keyboard

Screen resolution 1920 x 1080

Seen with the Alpha and the latest (2021.0.5.29) versions.

[Call Library Function Node 32- and 64-bit]

Hi Michael,

 

I just wanted to let you know that I was able to find a workaround the behavior by using Post-Install Custom Action to re-write the DLL path using the wildcard format.

[Call Library Function Node 32- and 64-bit]

Hi Michael,

 

I have the same issue the VIs use to build the VI packages use the * wildcard to make the reference to the shared library platform independent. During the VIP build process it seems that LabVIEW replaces the reference by the appropriate file extension and the appropriate bitness (32 or 64).

 

There is an option on Source File Settings page called Do Not Compile on Build which should avoid this behavior but it is not included in the Free version