Summary: We should add an option to LabVIEW so that if you have the VI Analyzer installed, whenever you use source code control to check in a modified VI, the VI Analyzer runs with a predefined list of settings to make sure that the modified VI meets the standards you've chosen.
Details: There are many aspects of a VI that ought to be a certain way when the VI is considered "finished" that ought not to actually break the VI. For example, you might want the text in your free lables to be spell checked correctly on a finished VI, but you don't really want the VI broken while debugging if you have misspelled words. You might not want coercion dots in the final VI, but breaking VIs when you have coercion dots during development is overkill. At the moment, you have an option of turning on Show Warnings in the Error List Window for a lot of these sorts of things, and LabVIEW R&D could add more to the warnings list, but there are so many things that we warn you about that the list is just noise, and since warnings are off by default, most people never see them. Your other option is to remember to run the VI Analyzer before you check in your VIs, but not everyone remembers to do that everytime. If the analysis could autorun as part of check in, it would help ensure good standards for VIs. I suggest that LV should have some way for the user to establish a list of settings for which VI Analyzer tests to run every time VIs are checked into source code control.
