—continued from above—
Subsequent Build Solution:
29>------ Build started: Project: UE4, Configuration: Development_Editor x64 ------
12> AutomationScripts.Automation -> ~PATHTOUNREAL~\Engine\Binaries\DotNET\AutomationScripts\AutomationScripts.Automation.dll
30>------ Build started: Project: Android.Automation, Configuration: Development Any CPU ------
31>------ Build started: Project: HTML5.Automation, Configuration: Development Any CPU ------
31> HTML5.Automation -> ~PATHTOUNREAL~\Engine\Binaries\DotNET\AutomationScripts\HTML5\HTML5.Automation.dll
30> Android.Automation -> ~PATHTOUNREAL~\Engine\Binaries\DotNET\AutomationScripts\Android\Android.Automation.dll
32>------ Build started: Project: AutomationTool, Configuration: Development Any CPU ------
9> Target is up to date
32> AutomationTool -> ~PATHTOUNREAL~\Engine\Binaries\DotNET\AutomationTool.exe
29> Target is up to date
To me, it looks like Launcher.Automation, HTML5.Automation, and Android.Automation fail because the OneSkyLocalization.Automation.dll hasn’t been built and it can’t find the OneSkyLocalization namespace when it searches for it.
Subsequent runs work because OneSkyLocalization.Automation.dll already exists before the build begins.
When Build Solution fails the first error is:
37>C:\Program Files (x86)\MSBuild\14.0\bin\Microsoft.Common.CurrentVersion.targets(1820,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "OneSkyLocalization.Automation". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors.
37>~PATHTOUNREAL~\Engine\Source\Programs\AutomationTool\Scripts\LauncherLocalization.Automation.cs(10,17,10,35): error CS0234: The type or namespace name 'OneSkyLocalization' does not exist in the namespace 'EpicGames' (are you missing an assembly reference?)
—continued—