Quote:
Originally Posted by Ether
How does one avoid doing this? Are there any pitfalls to watch out for? Is there a simple way to quickly "audit" a project to make sure this hasn't been done?
|
If you have vi's that you like to reuse in different projects, that aren't maintained in a common library, just be sure to copy the file into your project folder and only add new vi's to your project from that project folder, e.g., don't drag a vi into the Project Explorer window from a different project folder.
It's easy to check.
In the Project Explorer switch to the Files tab and you'll see the entire project hierarchy. If you see another project folder included, then you should fix that.