Build WindowsTerminalUniverasl AppPackage fails with missing Images #6153

Closed
opened 2026-01-31 00:31:08 +00:00 by claunia · 2 comments
Owner

Originally created by @lovettchris on GitHub (Jan 26, 2020).

Environment

Microsoft Windows [Version 10.0.18362.592]

Steps to reproduce

Load OpenConsole.sln, right click "WindowsTerminalUniversal" and select build Publish/CreateAppPackages.

Expected behavior

Should succeed

Actual behavior

16>C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets(6292,5): error : System.IO.DirectoryNotFoundException: Could not find a part of the path 'd:\git\terminal\src\cascadia\WindowsTerminalUniversal\Images'.

Interestingly there is an Images folder under Debug\PackageLayout\Images ?

Originally created by @lovettchris on GitHub (Jan 26, 2020). # Environment ```none Microsoft Windows [Version 10.0.18362.592] ``` # Steps to reproduce Load OpenConsole.sln, right click "WindowsTerminalUniversal" and select build Publish/CreateAppPackages. # Expected behavior Should succeed # Actual behavior 16>C:\Program Files (x86)\Microsoft Visual Studio\2019\Enterprise\MSBuild\Microsoft\VisualStudio\v16.0\AppxPackage\Microsoft.AppXPackage.Targets(6292,5): error : System.IO.DirectoryNotFoundException: Could not find a part of the path 'd:\git\terminal\src\cascadia\WindowsTerminalUniversal\Images'. Interestingly there is an Images folder under `Debug\PackageLayout\Images` ?
Author
Owner

@zadjii-msft commented on GitHub (Jan 27, 2020):

I'm not saying that we're expecting that to not work, but I'm pretty sure that's not the option you're looking for. You probably want to "Deploy" "CascadiaPackage" if you want to build and run the Terminal locally. WindowsTerminalUniversal is actually pretty much just an internal testing tool at this point.

@zadjii-msft commented on GitHub (Jan 27, 2020): I'm not saying that we're expecting that to not work, but I'm pretty sure that's _not the option you're looking for_. You probably want to "Deploy" "CascadiaPackage" if you want to build and run the Terminal locally. `WindowsTerminalUniversal` is actually pretty much just an internal testing tool at this point.
Author
Owner

@ghost commented on GitHub (Jan 31, 2020):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Jan 31, 2020): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6153