You are here: NI Home > Support > Product Reference > Manuals > LabVIEW 8.5 Help

You can create an organizational structure for items in a LabVIEW project. A well-organized structure can make it easier for you to share files among multiple projects, create build specifications, and use source control.

The following list describes some of the caveats and recommendations to consider when you organize items in a project:

• Create a separate directory of files for each project you create. Include the project file (.lvproj) and any other files that are only used in the project in the same directory. Place any files that are shared with other projects outside of the project directory. Organizing project files into separate directories makes it easier to identify files related to specific projects on disk.
• Directories on disk do not match the project structure of virtual folders. After you add a directory on disk to a project in a virtual folder, LabVIEW does not update the folder in the project if you make changes to the directory on disk. Add a directory on disk to the project in an auto-populated folder to monitor and update changes on disk in the project.
• (Windows) If you are building an installer, make sure you save the files that are in a project on the same drive as the .lvproj file. If some files are on a different drive, such as a network drive, links can break if you include the project in an installer.
• The structure of files in a source distribution does not have to match the structure in the Project Explorer window. You can specify a different structure when you build a source distribution.
• If you plan to remove items that appear under Dependencies, move the items from Dependencies to the target. You also can remove the item and all callers or redirect the callers. Dependencies lists the VI hierarchies of all VIs in the project.
• When you build an application, you can apply settings to an entire folder. Consider grouping all dynamic items in a folder under the target.
• The project can contain conflicts when two or more items with the same qualified name from different paths exist in the project. A yellow warning triangle appears on any conflicting items. Click the Resolve Conflicts button to view a summary of the project conflicts in the Resolve Project Conflicts dialog box.