LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Send vi in lvib

Hi all,

 

I would like to send some of my vi to my co-worker through an email, and I need to find the best way to do it.  I have a bunch of vi.  They are usually in lvib.  Not to mention that many of those vi are interlinked.  I would like to select a few of those vi and send them out through email.  My question is

 

How do I send them in such a way that when I prepare the send, I don't have to spend time to make sure I have included every single dependent vi and that when my co-worker open the file there will not be any broken links. 

 

Thanks!

 

Yik

------------------------------------------------------------------

Kudos and Accepted as Solution are welcome!
0 Kudos
Message 1 of 9
(3,779 Views)

From the project create a Souce Distribution.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 2 of 9
(3,778 Views)

Sweet.  That's exactly what I am looking for.  I never used it, so I didn't know about it.  One more question:

 

Is there a way to make the source distribution for an older version of LV, for example, 8.2?

 

Yik

------------------------------------------------------------------

Kudos and Accepted as Solution are welcome!
0 Kudos
Message 3 of 9
(3,767 Views)

That has been avaliable in all of the VL version I have used going back to BridgeVIEW 2.1.

 

In pre-LV8 version is was available under "Save with Options"

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 4 of 9
(3,764 Views)

Can you give me a few steps?  I think I can do the source distribution now, but I can't find the option where you can do source distribution and putting the distribution at a earlier version. 

 

To make a vi into an older version, I know I can do the "save for previous version", but not sure how to do that with source distribution.  Thanks!

 

Yik

------------------------------------------------------------------

Kudos and Accepted as Solution are welcome!
0 Kudos
Message 5 of 9
(3,740 Views)

I think the save for previous will do most of what you get in the Source Distribution. If a simple save for previous gives you too much, do the save in two steps Source Distribution , Save for Previous.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 6 of 9
(3,738 Views)

Since LV 8.x, Source Distributions are done using the Application Builder. So if you do not have that tool, you cannot automatically create a Source Distribution.

What you can do in order to create a copy for other PCs without the Application Builder is to select Save As... >>  Duplicate Hierarchy to New Location.This is available at least in LV 2009...... (didn't check with 8.x)

 

hope this helps,

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 7 of 9
(3,735 Views)

Norbert B wrote:

Since LV 8.x, Source Distributions are done using the Application Builder. So if you do not have that tool, you cannot automatically create a Source Distribution.

What you can do in order to create a copy for other PCs without the Application Builder is to select Save As... >>  Duplicate Hierarchy to New Location.This is available at least in LV 2009...... (didn't check with 8.x)

 

hope this helps,

Norbert


Application Builder - Is that is waht I find at the bottom of my project?

 

For VI's in VI'lib, I think that will get complicated.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 8 of 9
(3,732 Views)

Ben wrote:
[...]

Application Builder - Is that is waht I find at the bottom of my project?

 

For VI's in VI'lib, I think that will get complicated.

 

Ben


Ben,

 

the Application Builder is as of 8.x accessable from LV projects only and you will need a Build Specification in order to configure it. So you are somehow correct with your q

question 🙂

 

Well, esp. when distributing VIs from your local vi.lib, you should use the Application Builder since the option i stated for 2009 removes all dependencies into the vi.lib from your "distribution". Nevertheless, the question: how do i distribute vis which are part of the vi.lib should not really occur. The reason: the vi.lib is for components from NI. It is not recommended to include self-written VIs there.

 

Ok, i am a bit of cheating here (not talking about toolkits), but why must they be part of a Source Distribution?

 

Norbert

 

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
0 Kudos
Message 9 of 9
(3,729 Views)