Mass Compile changes files that do not have a LabVIEW code extension such as ".ctl" and ".vi"! Why is it trying to load, check, and save files with extensions such as ".bak" and “.err”? The following example shows files that a prior mass compile found problems with and I renamed them and removed them from source code control.
### Bad VI: "EditString.ctl.err" Path="C:\cvs\r8000\labview\app\editor\controls\EditString.ctl.err"
### Bad VI: "MCNavigate_old.vi.err" Path="C:\cvs\r8000\labview\app\remote_control\MCNavigate_old.vi.err"
Another example of this is described in https://forums.ni.com/t5/LabVIEW-Idea-Exchange/Mass-Compile-should-not-touch-Subversion-files/idi-p/... which says files with ".svn-base" are changes. Yes, there was a specific improvement made to ignore those, but really, that wouldn't be necessary if Mass Compile stuck to known LabVIEW file types.
Declined for reasons listed in AristosQueue's post:
"VIs can have any file extension. They are not required to use .vi. If LabVIEW opens a file and detect that the file is a VI, it will mass compile those files the same as any other VI. This is correct, intended behavior and will not be changing in the LabVIEW 20xx platform.
In LabVIEW NXG, file extensions are strict. NXG also does not have the concept of mass compile."