[MRTCore] In a packaged win32 app, the PRI is placed one directory above the EXE.

[rohanp-msft]

Quoting Hui on the problem this presents:
"Not in the same folder, the app doesn’t know what resource file to use. MRTCore doesn’t support “..\resources.pri”."

This is a possible customer scenario. Quoting Hui:
"A customer may have an app, then decide to package it."

BTW, it is as of yet unknown if this issue exists only when the to-be-packaged win32 app project is "external".
We suspect it is though because of this: WinUI solutions are also WAP projects and they don't have this issue. In that case though, the .vcxproj/.csproj project isn't external.

[sylveon]

Might be fixed by something like this?

https://github.com/microsoft/terminal/blob/3d09c7de1b35ce3593efb8185df98c47302c1050/src/cascadia/CascadiaPackage/CascadiaPackage.wapproj#L85-L87

I think, generally, this decision of putting every project in its own folder for MSIX packaging should be reconsidered, or made an option, considering normal VS output puts all artifacts in the same folder but the .wapproj does not. This means many common scenarios (a .exe with an associated .dll for example) break by default with .wapproj.

[rohanp-msft]

This has been fixed already by:
#814
and
#908
So closing this issue.

@sylveon As of the v1.0 preview releases, we've added single-project MSIX support. Please see https://docs.microsoft.com/en-us/windows/apps/windows-app-sdk/single-project-msix?tabs=csharp.