LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

VIPM remove block diagram

Solved!
Go to solution

Hi,

I have a VIPM package which I want to distribute to the customer. I am required to remove block diagram of source files. This is not a native feature of VIPM. As I understand from https://jki.userecho.com/communities/1/topics/136-option-to-remove-block-diagrams-in-vipb it should be possible to do this with a post - build VI. However, I don´t know how such a VI should look. Can anyone give me an example of such VI, or perhaps suggest another workaround?

0 Kudos
Message 1 of 3
(2,125 Views)
Solution
Accepted by topic author Rashek

The discussion you link to is quite old.

I think the best place to ask question about VIPM is JKI forum : https://forums.jki.net/forum/5-vi-package-manager-vipm/

 

What version of VIPM do you have?

Do you have a pro version or a free version?

 

I have the lastest version but in free edition, so when I try to generate a pre-build vi, I have a pop-up message telling me this feature requires a pro version :

Annotation 2019-11-06 100233.png

If you do have a pro version, I guess what you have to add to the pre-build VI is something like that :

Annotation 2019-11-06 101847.png

If you have a free version... create a utility VI that can save all your VIs with / without diagram and run it before building your package.

 

Good luck to you


We have two ears and one mouth so that we can listen twice as much as we speak.

Epictetus

Antoine Chalons

Message 2 of 3
(2,093 Views)

If you don't have the pro version the you could run some VI that removes block diagrams before the build, but then you may have the problem of having no more block diagrams in the source to your build.  So be sure and back it up before doing this, as you can't undo removing the block diagram.

 

Alternatively you could have it be part of the Post Install VI which could remove the block diagrams after the package is installed.  This of course would mean the block diagrams are in the VIs when it is in the package but won't touch the package source when building.

0 Kudos
Message 3 of 3
(2,040 Views)