Closed george-c29 closed 4 years ago
The MSBuildCustomLocator was sometimes identifying MS buildtools 2017, even though 2019 was available as well on the machine, thus causing some builds requiring components from msbuildtools 2019 to fail.
@GeorgeCimpoies can you add the CHANGELOG as well please?
@ngyukman I've added the changelog entry.
The MSBuildCustomLocator was sometimes identifying MS buildtools 2017, even though 2019 was available as well on the machine, thus causing some builds requiring components from msbuildtools 2019 to fail.