Jump to content

Recommended Posts


I have a question about general rule of packaging and distributing LabVIEW code.

I have a LabVIEW project (please see below tree structure) which contains numerous VI sample code which invokes function calls in the dll (PVCamNET.dll).

As the project needs to be shipped to the world I would like to package it more professionally than zipping the entire folder. 

Note the folders, DemoApp and Examples contain VI code.

Looking at the build specifications  there seem to be many options for packaging.

I have a DLL enclosed in the folder and besides the VIs the DLL must be part of the project.


My question is quite simple - what is the best way to package this project for the user to play with the VI code ?





Link to post
Share on other sites

Hi Michael, Yes. I played with it the source distribution. After building with it I see a new folder "My Source Distribution" and all my VI files and the dll are inside. 

It seems that everything was just copied into one directory - this is not so different from just zipping the folder.



Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...

Important Information

By using this site, you agree to our Terms of Use.