[PR #5031] Set the ComponentResourceLocation for our DLL projects #26087

Open
opened 2026-01-31 09:13:50 +00:00 by claunia · 0 comments
Owner

Original Pull Request: https://github.com/microsoft/terminal/pull/5031

State: closed
Merged: Yes


These projects load Xaml components that have Uids, but those Uids just
weren't working because Xaml components are, by default, loaded in
"Application" scope. Application scope is great if the resource producer
is the EXE project.

Application scope means that resources are looked up at the resource
root, but DLLs with resources don't produce resources at the root. They
produce resources at a root named after the DLL.

Setting the Xaml component resource location to Nested makes sure the
Xaml resource loader loads resources from the right places.

**Original Pull Request:** https://github.com/microsoft/terminal/pull/5031 **State:** closed **Merged:** Yes --- These projects load Xaml components that have Uids, but those Uids just weren't working because Xaml components are, by default, loaded in "Application" scope. Application scope is great if the resource producer is the EXE project. Application scope means that resources are looked up at the resource root, but DLLs with resources don't produce resources at the root. They produce resources at a root named after the DLL. Setting the Xaml component resource location to Nested makes sure the Xaml resource loader loads resources from the right places.
claunia added the pull-request label 2026-01-31 09:13:50 +00:00
Sign in to join this conversation.
No Label pull-request
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#26087