Localized file check-in by OneLocBuild Task: Build definition ID 140: Build ID 3076847

[dotnet-oneloc-localization]

This is the pull request automatically created by the OneLocBuild task in the build process to check-in localized files generated based upon translation source files (.lcl files) handed-back from the downstream localization pipeline. If there are issues in translations, visit https://aka.ms/icxLocBug and log bugs for fixes. The OneLocBuild wiki is https://aka.ms/onelocbuild and the localization process in general is documented at https://aka.ms/AllAboutLoc.

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
2 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[github-actions]

📋 SDK Diagnostic Documentation Reminder

This PR introduces 11 new SDK diagnostic codes:

• NETSDK1147
• NETSDK1235
• NETSDK1236
• NETSDK1237
• NETSDK1238
• NETSDK1239
• NETSDK1240
• NETSDK1241
• NETSDK1242
• NETSDK1243
• NETSDK1244

Action Required

Please ensure that documentation for these diagnostics is added or updated in the dotnet/docs repository at:

• Path: docs/core/tools/sdk-errors/
• Documentation: https://learn.microsoft.com/dotnet/core/tools/sdk-errors/

Each diagnostic should have:

• A clear description of the error/warning
• Possible causes
• Recommended solutions
• Code examples where applicable

Thank you for helping keep our documentation up to date! 🙏

[github-actions]

🔍 Build Failure Analysis

Summary — Every build leg fails identically at the _UpdateXlf target because src/Cli/dotnet/Commands/xlf/CliCommandStrings.cs.xlf (and the dotnet-aot project's copy of the same file) is out of date with src/Cli/dotnet/Commands/CliCommandStrings.resx.

Root cause: this loc payload predates a resx change merged afterward on the base branch

This is an automated OneLocBuild check-in PR (bot: dotnet-oneloc-localization) targeting release/11.0.1xx, created 2026‐09‐08. Since then, #56303 ("Honor MTP zero-tests and exit-code policies in dotnet test") merged into release/11.0.1xx on 2026‐09‐14 and added roughly 14 new resources to CliCommandStrings.resx (ExitCodeAtLeastOneTestFailedDescription, ExitCodeZeroTestsDescription, ExitCodeTestSessionAbortedDescription, etc. — used by the new TerminalTestReporter exit-code descriptions).

This PR's .xlf content was generated from the older loc payload, so it doesn't yet contain those strings in the shape the base branch's .resx now expects, and Microsoft.DotNet.XliffTasks's _UpdateXlf target correctly fails the build rather than silently drifting:

'Commands/xlf/CliCommandStrings.cs.xlf' is out-of-date with 'Commands/CliCommandStrings.resx'.
Run `msbuild /t:UpdateXlf` to update .xlf files or set UpdateXlfOnBuild=true to update them on
every build, but note that it is strongly discouraged to set UpdateXlfOnBuild=true in
official/CI build environments as they should not modify source code during the build.

The same failure repeats for both src/Cli/dotnet/dotnet.csproj and src/Cli/dotnet-aot/dotnet-aot.csproj, since dotnet-aot links the same resx/xlf files.

Additionally, this PR's own .xlf diff shows a duplicate <trans-unit id="ExitCodeAtLeastOneTestFailedDescription"> entry in CliCommandStrings.cs.xlf (one block newly inserted with state="new", and the pre-existing entry immediately following, unchanged) — a symptom consistent with the loc generation running against a resx snapshot that had already partially picked up the new strings from a different angle. Regenerating from the current base-branch resx should resolve both problems together.

Affected files / errors

• src/Cli/dotnet/Commands/xlf/CliCommandStrings.cs.xlf — out-of-date vs. Commands/CliCommandStrings.resx (_UpdateXlf target, dotnet.csproj)
• Same file, referenced again via src/Cli/dotnet-aot/dotnet-aot.csproj (_UpdateXlf target)
• All 10 build legs (Windows x64/arm64, Linux x64/arm64, Mac arm64, Windows FullFramework, and the four AOT variants) report the identical pair of errors — this is a single root cause, not per-platform breakage.

Proposed fix

This is generated localization content — do not hand-edit the .xlf files (repo policy). The correct fix is to regenerate them from the current resx:

msbuild /t:UpdateXlf

run against the current release/11.0.1xx tip (post‐#56303), then re-run the OneLocBuild check-in with the refreshed loc payload so the new ExitCode*Description strings are captured and the duplicate trans-unit is resolved. If the OneLocBuild pipeline supports simply re-triggering against the latest base commit, that is likely the simplest remediation rather than patching this generated PR by hand.

---

Build overview

• MSBuild: 18.11.0-1.26420.103+1d599674e
• Build: FAILED, 225 projects evaluated, 3 errors / 1 warning (representative leg: Linux x64)
• Failed projects: Build.proj, sdk.slnx, MicroBenchmark.csproj, dotnet-aot.csproj, dotnet.csproj
• Failing target: _UpdateXlf (task UpdateXlf, from Microsoft.DotNet.XliffTasks v11.0.0-beta.26453.107)
• Identical failure reproduced across all 10 published binlogs (Windows x64/arm64 incl. AOT/FullFramework, Linux x64/arm64 incl. AOT, Mac arm64 incl. AOT)

All MSBuild errors

Code	Project	Target	Message
(none — MSB diagnostic without code)	src/Cli/dotnet/dotnet.csproj	_UpdateXlf	'Commands/xlf/CliCommandStrings.cs.xlf' is out-of-date with 'Commands/CliCommandStrings.resx'.
(none — MSB diagnostic without code)	src/Cli/dotnet-aot/dotnet-aot.csproj	_UpdateXlf	'.../dotnet/Commands/xlf/CliCommandStrings.cs.xlf' is out-of-date with '.../dotnet/Commands/CliCommandStrings.resx'.

Both errors recur verbatim (modulo path separator/root) on every one of the 10 build legs.

---

_{🤖 Generated by the Build Failure Analysis workflow using (a href="(dev.azure.com/redacted) · commit e8c9ebe · [Azure DevOps build]((dev.azure.com/redacted)}

🤖 Automated content by GitHub Copilot. Generated by the Build Failure Analysis workflow. · auto · 393.2 AIC · ⌖ 1.95 AIC · ⊞ 7.2K · [◷]( · ◷)