Broaden the scope of VI Analyzer to projects, libraries and classes

[Nicolas_Bats]

VI Analyzer is great tool but can only perform static analysis on VI (as far as I know). It could be nice to run some tests on libraries / classes or even projects files as well to enforce good practices. 

[Petru_Tarabuta]

+1. This would open powerful new ways to ensure code quality. For example, a VI Analyzer test could check that all files that are members of a lvlib or lvclass are located in the same disk folder hierarchy as the owner (the lvlib or lvclass).

[SSSchroeder]

Agree. This would be great capability to be offered natively. This week at NI Connect, I learned that VI Analyzer is on the road map to be open sourced! Soon you can be the change you want to see.

[crossrulz]

VI Analyzer is a slightly different beast as far as opening up than the rest of the proposals because it is a toolkit that is included with Pro. I would need to do some digging to see what the most recent semi-public information is on this exact tool being opened up. I want to say it is just the built-in tests that would be open.

I'm trying to curb expectations. It would be great to make all of VI Analyzer open, but it is a money maker on its own which adds to the complexity. Now I'll just sit back and see what NI decides to do over the next few years as the slow roll of new open projects occur.