Skip to content

Fix ResXFileRef/Bitmap href paths in translated .resx/.vsct: relative instead of absolute#17071

Draft
mwiemer-microsoft with Copilot wants to merge 3 commits into
mainfrom
copilot/translate-resx-file-refs
Draft

Fix ResXFileRef/Bitmap href paths in translated .resx/.vsct: relative instead of absolute#17071
mwiemer-microsoft with Copilot wants to merge 3 commits into
mainfrom
copilot/translate-resx-file-refs

Use EndsWith(char) overload in MakeRelativePath for efficiency

57bf841
Select commit
Loading
Failed to load commit list.
Azure Pipelines / arcade-pr succeeded Jul 2, 2026 in 33m 10s

Build #20260702.15 had test failures

Details

Tests

  • Failed: 48 (1.10%)
  • Passed: 3,930 (90.14%)
  • Other: 382 (8.76%)
  • Total: 4,360

Annotations

Check failure on line 1 in XunitReportingTests.ExerciseXunitCharacterFilteringFailurePath

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

XunitReportingTests.ExerciseXunitCharacterFilteringFailurePath

Intentional Failure 🍕 \r \n \t \a \b \v \f \0\r\nExpected: True\r\nActual:   False
Raw output
at XunitReportingTests.ExerciseXunitCharacterFilteringFailurePath() in Class1.cs:line 1

Check failure on line 1 in HelixReporterTests.failure1

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

HelixReporterTests.failure1

This failure is expected and is not the reason why your PR failed. This test is always failing in order to test failure reporting infrastructure. If your PR is blocked there must be another test or build error that is blocking your PR.

Check failure on line 1 in HelixReporterTests.failure2

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

HelixReporterTests.failure2

This failure is expected and is not the reason why your PR failed. This test is always failing in order to test failure reporting infrastructure. If your PR is blocked there must be another test or build error that is blocking your PR.

Check failure on line 1 in HelixReporter.TRX.Fail2

See this annotation in the file changed.

@azure-pipelines azure-pipelines / arcade-pr

HelixReporter.TRX.Fail2

This failure is expected and is not the reason why your PR failed. This test is always failing in order to test failure reporting infrastructure. If your PR is blocked there must be another test or build error that is blocking your PR.
Raw output
at tests.UnitTest1.TestMethod4() in UnitTest1.cs:line 26