Need to confirm, for each of VS 2017, 2019, and 2022 (pre) that
The location of the tools is revealed
There is a consistent access to vcvarsall.bat even though it has already happened.
Determine a distinguisher that is not there when older vcvarsall.bat and/or VCbind have run.
There is a way to take that location into VCbind in some useful manner. This may be a necessary additional task, and it might take more to get it done.
Need to confirm, for each of VS 2017, 2019, and 2022 (pre) that
vcvarsall.bat
even though it has already happened.