Replies: 2 comments
-
I'm pretty sure that's just cause VS defaults to "AnyCPU", when it needs to be x64 (or x86). See also #14634 |
Beta Was this translation helpful? Give feedback.
0 replies
-
I was able to build & run it after checking "Build" next to each project (except tests) and changing the active configuration from x86 to x64. This didn't get rid of the popup notification though, I guess it can be ignored. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
It seems that the solution configuration is messed up. When I try to run the CascadiaPackage project (as mentioned here) it produces an error:
Once I check the Deploy and Build checkbox next to CascadiaPackage in Configuration Manager, I get another error:
And so on.
Am I missing something? I just want to run Windows Terminal under a debugger (to investigate a bug).
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions