LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Custom express VI not in user.lib

I have developed a nice set of Express VIs for our customers, but after some trials and tribulations with the LabVIEW installer tool it seems (and I have been told) that express VIs can only be placed in user.lib where they were originally created.  I want to put them in Program Files\<My Company>\<My Product>\Express so they are with the rest of my application.  Is this possible?  What’s the trick?  I also can’t have the user having to browse for the configuration VI when they drop down the express VI.

 

Thanks,

--Matt
0 Kudos
Message 1 of 3
(2,761 Views)
Hi Matt,

I hope you are doing well today! According to page 35 of the LabVIEW Express VI Development Toolkit User Guide, when you create Express VIs that you will deploy on other computers, you must use the same directory structure that the target computers use. The components of an Express VI link to each other through both relative and specific paths. If the directory structure is different on each computer to which you deploy, the links break, and the Express VI prompts users to find the configuration dialog box VI. Also, if you want to move Express VIs to other computers, you would need to move the two VI libraries for the Express VI and any related .mnu files.
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies
Message 2 of 3
(2,748 Views)
I'm trying to deploy my Express VI too, but it does not seem to work as desribed. Out of curiosity I created new express from blank VI, pointed it to c:\temp in only configuration dialog of the toolkit, but still if I drop this empty express into any VI, I have to browse for config VI. So I tried to let it be in default location (user.lib) and guess what? It works. Assumption: Express VI works only if placed in default folder, you can't move it anywhere, despite you're trying to deploy or create a new one.

I'm using LabVIEW 7 and 7.1, in both the same bug occurs. Does anybody know a workaround?
0 Kudos
Message 3 of 3
(2,724 Views)