Should I be working with llb's or vi files in a folder for Labview Project Explorer?

[ShotSimon]

I have a large llb which I decided to move back into individual vi's in a folder.  When I created a Project and added the files to try and make a runtime, Labview freaked out and listed all files as conflicting path names to the original dll.

To make matters worse the conflicts can not be resolved with the dialog buttons provide.   In other words it won't let me deselect the other path to remove the conflict.  What do you suggest I do?  SS

[tst]

I don't have experience with the project manager, but LabVIEW treats an LLB like a folder - renaming the folder to have the same name as the LLB (including the .llb part) works and might help for what you want - it should cause LabVIEW to see the VIs as if they are still in the same place.

On a side note - a folder is usually better than an LLB, because LLB can become corrupt and then you lose all the VIs. LLBs are usually useful if you want to distribute code once it's working.

[ShotSimon]

Changing the file name is a cool little trick to stop Labview from spilling it's brain inside a project.  Thanks, SS

[JeffBoettcher]

I will echo tst's statement that it is generally better to work with VIs individually during development, but can sometimes be useful to package your VIs into an LLB when distributing them.  In addition to tst's reasons, working with VIs individually makes development much simpler when working with source code control systems.

[ShotSimon]

This link explains exactly the problems I have run into and why.  NI calls it cross linking:  https://www.ni.com/en/support/documentation/supplemental/08/best-practices-for-managing-ni-labview-a...

Message Edited by ShotSimon on 01-18-2008 12:07 PM