—continued from above—
After that failure, the OneSkyLocalization.Automation.dll is successfully built:
46>------ Build started: Project: Android.Automation, Configuration: Development Any CPU ------
47>------ Build started: Project: HTML5.Automation, Configuration: Development Any CPU ------
42> OneSkyLocalization.Automation -> ~PATHTOUNREAL~\Engine\Binaries\DotNET\AutomationScripts\OneSkyLocalization.Automation.dll
45> XLocLocalization.Automation -> ~PATHTOUNREAL~\Engine\Binaries\DotNET\AutomationScripts\XLocLocalization.Automation.dll
But the build has already failed because it couldn’t find the OneSkyLocalization namespace when it was searching for it.
Subsequent “Build->Build Solution” runs work because the OneSkyLocalization namespace already exists from the previous (unsuccessful) Build Solution / Rebuild Solution.
“Build->Rebuild Solution” always fails because it’s attempting to rebuild everything every time, and fails to find the OneSkyLocalization namespace before it’s been created again; just like a first run of “Build->Build Solution” after a clean install.
Full logs attached below:
First “Build->Build Solution” attempt from clean install of 4.13.1
Second “Build->Build Solution” attempt from clean install of 4.13.1
*Note: “~PATHTOUNREAL~” is a masking string used to hide user data. Within the actual log it is an explicit, absolute path to the UE4 install directory.