starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Missing Files #1127

New Issue
Open
opened 2026-01-30 22:17:07 +00:00 by claunia · 0 comments
claunia commented 2026-01-30 22:17:07 +00:00
Owner
Copy Link

Originally created by @Tembocs on GitHub (May 15, 2019).

I'm trying to build Windows Terminal from command line using VS 2017 on Windows 10 x64 insider, build 18362.86. I kept getting the error below even after installing all the VS 2017 components that have something to do with C++ and .Net. From the error message it seems the build surprisingly involves VS 2019 (which I have installed as well). My expectation is VS 2019 should not be involved as I use VS 2017 command line. I then decided to install all the components that have something to do with C++ and .Net for VS 2019. I still get the same error message.

My steps for building:

  1. Clone the repo from github
  2. Do git submodule update --init --recursive
  3. Do .\tools\razzle.cmd
  4. Do bcz

What am I missing? The error message is as below:
C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v150\Microsoft.CppCommon.targets(2128,3): error MSB4019: The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\WindowsXaml\v15.0\Microsoft.Windows.UI.Xaml.Cpp.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk. [c:\Users\Tembo\Desktop\qnd\cpp\Terminal10\src\cascadia\TerminalSetting\TerminalSettings.vcxproj]

Originally created by @Tembocs on GitHub (May 15, 2019). I'm trying to build Windows Terminal from command line using VS 2017 on Windows 10 x64 insider, build 18362.86. I kept getting the error below even after installing all the VS 2017 components that have something to do with C++ and .Net. From the error message it seems the build surprisingly involves VS 2019 (which I have installed as well). My expectation is VS 2019 should not be involved as I use VS 2017 command line. I then decided to install all the components that have something to do with C++ and .Net for VS 2019. I still get the same error message. My steps for building: 1. Clone the repo from github 2. Do `git submodule update --init --recursive` 3. Do `.\tools\razzle.cmd` 4. Do `bcz` What am I missing? The error message is as below: `C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\VC\v150\Microsoft.CppCommon.targets(2128,3): error MSB4019: The imported project "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Microsoft\WindowsXaml\v15.0\Microsoft.Windows.UI.Xaml.Cpp.targets" was not found. Confirm that the path in the <Import> declaration is correct, and that the file exists on disk. [c:\Users\Tembo\Desktop\qnd\cpp\Terminal10\src\cascadia\TerminalSetting\TerminalSettings.vcxproj]`
claunia added the Resolution-Duplicate label 2026-01-30 22:17:07 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Resolution-Duplicate
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#1127
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?