terminal: [Build Error] Unresolved Settings.KeyChord &.Settings.IKeyBindings

Try adding a project reference in TerminalApp to the TerminalSettings project.

@alex285 don’t bother to build it anymore. Someone has shared a built version <link removed>

One thing I can confirm is the build works with both VS2019 16.0.3 and 16.1.0 Preview 3. I’ve tried both successfully.

Have the same issue by using VS2019 16.1.0 Preview 3.0

But can be built by using VS 2017

@chunliu thank you!! nice one!! …and ofc now im even more willing to build it 😃))

Haha, hit the show all files. VCproj still uses the old system where files have to be included in the project to show up in the solution explorer.

Edit: Haha this is a funny thing I’ve encountered many times so I knew right away how this happens. Show all files is the icon in the solution explorer toolbar to the left of the properties (wrench) icon.

@ThreeSevenths I had modified VS so I was missing some 141 components, although I re-installed them prior to my previous rebuild (above comment); but should we re-target the project for 141, or 141 just needs to be installed? because I see guys saying that they build if on 142, plus there are some commits for VS2019 support, so I assume that includes 142 tools

Yes, I have recursively cloned

Ok, I did not retarget the projects. You might have some success doing a git reset --HARD as long as you have not made any changes to get it back to the same state as the git repo. You also need to target the cascadia package