From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
. When a common VI is used in one or many projects, it is controlled by SCC so you do not have to have add it explicitely to SCC. If the VI is not part of any SCC project, there is little need to control this VI... However, what you can do is to create a VI with all the common VIs on its diagram and make a project with this VI as Top Level. All VIs controlled by SCC must be in the SCC directory or subdirectories.
You cannot add LLB's to source code control (SCC), except as an "Extra File" file. However, this is not a very good solution because the whole library is under SCC, not the individual files. LLB's must be converted to directories in order to maintain SCC of separate VI's.
Thanks Tim. In fact my problem is that my top.vi uses some VIs which are in ascending directories. It seems that SCC does not want to include them in its database. How can you declare a directory of VIs as a kind of "library" not in term of LLB but just as "shared VIs".
Do you allways have to use descending directory architecture from "top.vi" to "used.vi" to be abble to use SCC??? It seems way too restricting. 😉
Two suggestions: 1. Create a 'stub' VI. The block diagram of this VI will contain nothing but icons of your commonly used VI's. Then add this stub VI to SCC as a top level VI. The stub VI and its sub VI's must be in the local SCC working directory or one of its sub directories.
2. It is possible to add a top level VI whose sub VI's are closer to the root directory. However, ALL directories that contain VIs that are to be added to SCC must be in the local SCC directory or one of its sub directories. If a directory is not in the local SCC working directory 'Tree' then SCC will complain.
