Yes --
We have a "standard" VI Analyzer configuration file that we have defined as what we work towards. It turns off some stuff (like we decided not to be bothered by backwards wires) and configures other settings (especially for our in-house written tests).
We encourage people to use this configuration file as either the basis for creating their own VI Analyzer configuration file, or to start VI analyzer and load the config file (which is just rules, no files to analyze) and then add the files to analyze they are interested in.
It also isn't hard to put together a LV "tools" menu entry that will automatically launch VI analyzer against a specified configuration file and add all files in a user selected directory, or all files in active project, or all files in memory (not part of vi.lib).
