From Saturday, Nov 23rd 7:00 PM CST - Sunday, Nov 24th 7:45 AM CST, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Saturday, Nov 23rd 7:00 PM CST - Sunday, Nov 24th 7:45 AM CST, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
05-27-2020 03:12 AM
I'm trying to make use of VI Analyser in our CI script, so the analyser is running as part of our integration testing on feature branches.
I have tried to create a generic task, where I have added the source code folder as the Top-Level item.
However, I if then create a new subVI (or even a new project) in that folder, then this VI is not analyzed.... Do I really have to remember to update the VI Script every time I create a new VI in the very same folder?
Solved! Go to Solution.
05-27-2020 05:57 AM
Hmm, seems like it is working as I would like. When running the script through LabVIEW CLI all the VIs in the folder are analysed.
05-27-2020 10:58 AM
Right, if you add a folder to a VI analysis, then all the contents of that folder are analyzed. if you then add files to the folder later, those files should be analyzed by the same VI Analyzer task without need to reconfigure it. Let me know if that's not the behavior you're seeing.
05-29-2020 03:39 AM
Thanks for your reply.
Yep, that is indeed how it works... Not sure what I did in the first place 😛