In https://github.com/microsoft/axe-windows/pull/786#discussion_r1005849979, the suggestion was made to have CopyLocalizedFiles.ps1 detect which projects had localized folders to copy, as oppose to requiring that src\CI\CI.csproj call them out explicitly. This PR makes that change. The logic is as follows:
Start with the solution folder
Walk through all child directories of the solution folder (these are the project folders)
Check for the existence of a bin\Release\netstandard2.0\localize directory within each project. This is the folder created by MicroBuild if localization is enabled
If the folder exists, call into the code that was already in place in the script.
Within the script, some internal function names have been massaged to better reflect what they do.
src\CI\CI.csproj now executes the script just once. It enables Verbose logging so that we have a nice trace inside the build pipeline. This output is visible here
The files included in the package are still correct:
Details
In https://github.com/microsoft/axe-windows/pull/786#discussion_r1005849979, the suggestion was made to have
CopyLocalizedFiles.ps1detect which projects had localized folders to copy, as oppose to requiring thatsrc\CI\CI.csprojcall them out explicitly. This PR makes that change. The logic is as follows:bin\Release\netstandard2.0\localizedirectory within each project. This is the folder created by MicroBuild if localization is enabledWithin the script, some internal function names have been massaged to better reflect what they do.
src\CI\CI.csprojnow executes the script just once. It enables Verbose logging so that we have a nice trace inside the build pipeline. This output is visible hereThe files included in the package are still correct:
Motivation
Reduced maintenance if/when other projects are localized, easier debugging of the build script
Context
Pull request checklist