Cause: - Incomplete runtime copying mixed outdated and current Laatzen assemblies, causing missing-library and assembly-version errors. - An explicitly configured local output path was incorrectly treated as an external binary package, skipping local dependency preparation. Solution: 1. Make GCI build update the Laatzen runtime - Prepare local GenesisToolBox dependencies before resolving GCI references. - Validate and synchronize the runtime into packages/Common, GCI output and the runtime package. - Reject missing or incompatible assemblies before copying. 2. Preserve external binary package support - Normalize source paths to correctly recognize local output. - Consume packages from other directories without building external projects and preserve the BuildLocalLaatzenRuntime override. - Copy runtime subdirectories into TBF output, remove obsolete binding redirects and track synchronized files while preserving unrelated destination files. - Include the refreshed Common runtime distribution, documentation and the patch required for the ignored external GenesisToolBox project. 3. Added regression coverage - Added checks for missing assemblies, incompatible versions, recursive copying, stale-file cleanup and manifest path containment; synchronization checks passed. - GCI rebuild passed with the explicit local source path from the failing Visual Studio log; external-package mode and explicit preparation disablement also passed. - Verified identical copies of three affected DLLs across all five pipeline locations. - TBF copying passed; full TBF compilation remained unverified because other project outputs were missing. The subsequent revision-only change was verified in source. 4. Increased revision - Updated TBF AssemblyVersion and AssemblyFileVersion from 3.9.3147.116 to 3.9.3147.117.
7.0 KiB
7.0 KiB