Siegfried Pammer c0626ada56 #3315: Pin WPF resource IDs when exporting a project ...

A rebuilt WPF project only resolves its own pack URIs when every entry of
"<AssemblyName>.g.resources" comes back under the resource ID it had before.
The file on disk cannot carry that ID: it is sanitized for the file system,
and the ID itself is escaped. Verified against a WPF assembly built for this:
the WPF build tasks re-escape whatever LogicalName they are given, so the item
has to hand them the decoded name, and an entry left as EmbeddedResource
rebuilds into a manifest resource of its own instead of into ".g.resources".

The adjustment is made where the items are collected, so it covers the base
class and both hosts that plug their own BAML handling into it without
widening the WriteResourceToFile or IResourceFileHandler contracts.

The Resource build action this gives them is also what #2253 asks for.

Assisted-by: Claude:claude-opus-5[1m]:Claude Code

2026-09-03 12:08:21 +02:00

..

ProjectFileWriterSdkStyleTests.cs

#3315: List all decompiled project items in SDK-style projects

2026-09-03 12:08:09 +02:00

ReservedFileSystemNameTests.cs

Fix #3775: escape reserved Windows device names in output file names

2026-06-12 18:58:31 +02:00

TargetFrameworkTests.cs

dev: Strip BOM mark from text files

2025-08-28 20:56:19 -04:00

WholeProjectDecompilerTests.cs

#3315: Pin WPF resource IDs when exporting a project

2026-09-03 12:08:21 +02:00