starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-07-08 18:16:28 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

"Windows Terminal" app package cannot be debugged in default VS configuration #982

New Issue
Closed
opened 2026-01-30 22:13:01 +00:00 by claunia · 11 comments
claunia commented 2026-01-30 22:13:01 +00:00
Owner
Copy Link

Originally created by @finesse-fingers on GitHub (May 11, 2019).

If anyone can help me get started, I can't seem to get debugging to work in VS2019. I am able to build, run and deploy the app, however, any breakpoints I set don't work when I try to debug with F5 (I saw @miniksa on youtube debug, so I know it should work).

When I stop/terminate debugging I get the following:
image
Perhaps this is related?

  • Windows build number: 10.0.18362.86
  • VS 2019 16.0.3 (Community)
Originally created by @finesse-fingers on GitHub (May 11, 2019). If anyone can help me get started, I can't seem to get debugging to work in VS2019. I am able to build, run and deploy the app, however, any breakpoints I set don't work when I try to debug with F5 (I saw @miniksa on youtube debug, so I know it should work). When I stop/terminate debugging I get the following: ![image](https://user-images.githubusercontent.com/19501248/57566969-e49adb80-7415-11e9-96c2-0fe8e56956d1.png) Perhaps this is related? * Windows build number: 10.0.18362.86 * VS 2019 16.0.3 (Community)
claunia added the Issue-BugResolution-ExternalArea-Build labels 2026-01-30 22:13:01 +00:00
claunia commented 2026-01-30 22:13:01 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 11, 2019):

This problem haunts us. The secret is something you'd never expect, and something that belongs in our getting started guide.

Go to the properties for the CascadiaPackage project, choose Debug, and change the project type from "Mixed (Managed and Native)" to "Native Only".

@DHowett-MSFT commented on GitHub (May 11, 2019): This problem _haunts_ us. The secret is something you'd never expect, and something that belongs in our getting started guide. Go to the properties for the _CascadiaPackage_ project, choose Debug, and change the project type from "_Mixed (Managed and Native)_" to "_Native Only_".
claunia commented 2026-01-30 22:13:02 +00:00
Author
Owner
Copy Link

@pkarakal commented on GitHub (May 11, 2019):

Can you explain why this happens in more detail than the Error thrown provides?

@pkarakal commented on GitHub (May 11, 2019): Can you explain why this happens in more detail than the Error thrown provides?
claunia commented 2026-01-30 22:13:02 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (May 11, 2019):

Sure. The “Windows app packaging” project type (wapproj) in the Visual Studio project system is a derivative of the C# project type csproj. Owing to that, VS assumes that by default any application launched from WAP projects will start up the CLR.

Since this one doesn’t, it can’t be debugged until we tell VS to give up on the CLR.

@DHowett-MSFT commented on GitHub (May 11, 2019): Sure. The “Windows app packaging” project type (`wapproj`) in the Visual Studio project system is a derivative of the C# project type `csproj`. Owing to that, VS assumes that by default any application launched from WAP projects will start up the CLR. Since this one doesn’t, it can’t be debugged until we tell VS to give up on the CLR.
claunia commented 2026-01-30 22:13:02 +00:00
Author
Owner
Copy Link

@oising commented on GitHub (May 11, 2019):

@krystian-mwebdev Wrong place to ask. Any links placed here will be immediately removed because there will be a non-trivial amount of people who will assume because it's on the official repo, it's a supported release.

@oising commented on GitHub (May 11, 2019): @krystian-mwebdev Wrong place to ask. Any links placed here will be immediately removed because there will be a non-trivial amount of people who will assume because it's on the official repo, it's a supported release.
claunia commented 2026-01-30 22:13:02 +00:00
Author
Owner
Copy Link

@finesse-fingers commented on GitHub (May 11, 2019):

I am happy to update README to reflect this.

@finesse-fingers commented on GitHub (May 11, 2019): I am happy to update README to reflect this.
claunia commented 2026-01-30 22:13:02 +00:00
Author
Owner
Copy Link

@finesse-fingers commented on GitHub (May 11, 2019):

On second thought, it looks like it is being addressed in #704.

@finesse-fingers commented on GitHub (May 11, 2019): On second thought, it looks like it is being addressed in #704.
claunia commented 2026-01-30 22:13:03 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 12, 2019):

I'm not sure this is actually in #704, @bkot88 feel free to make another pr

@zadjii-msft commented on GitHub (May 12, 2019): I'm not sure this is actually in #704, @bkot88 feel free to make another pr
claunia commented 2026-01-30 22:13:03 +00:00
Author
Owner
Copy Link

@TheCloudSaver commented on GitHub (May 12, 2019):

I've not added any new info in my PR, just fixed typo's ;)

@TheCloudSaver commented on GitHub (May 12, 2019): I've not added any new info in my PR, just fixed typo's ;)
claunia commented 2026-01-30 22:13:03 +00:00
Author
Owner
Copy Link

@finesse-fingers commented on GitHub (May 13, 2019):

It seems when debugging in "Native Only" mode, the app throws an exception when drop down is clicked (to open a new tab).

image

This is in src/cascadia/WindowsTerminal/main.cpp.

@finesse-fingers commented on GitHub (May 13, 2019): It seems when debugging in "Native Only" mode, the app throws an exception when drop down is clicked (to open a new tab). ![image](https://user-images.githubusercontent.com/19501248/57591634-c8ae4b80-7575-11e9-881e-6b2f7ce89327.png) This is in src/cascadia/WindowsTerminal/main.cpp.
claunia commented 2026-01-30 22:13:03 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (May 13, 2019):

@bkot88 That's known, but the cause is very unknown at this time. Could you open a second issue to track that particular bug?

@zadjii-msft commented on GitHub (May 13, 2019): @bkot88 That's known, but the cause is very unknown at this time. Could you open a second issue to track that particular bug?
claunia commented 2026-01-30 22:13:04 +00:00
Author
Owner
Copy Link

@curtisgray commented on GitHub (Apr 9, 2020):

This problem haunts us. The secret is something you'd never expect, and something that belongs in our getting started guide.

Go to the properties for the CascadiaPackage project, choose Debug, and change the project type from "Mixed (Managed and Native)" to "Native Only".

The CascadiaPackage can crash Visual Studio when the Properties (right-click) menu is selected. To fix the crash so VS can load Properties, select x64 in the Platform dropdown.

cascadiapackage-properties-fix

@curtisgray commented on GitHub (Apr 9, 2020): > > > This problem _haunts_ us. The secret is something you'd never expect, and something that belongs in our getting started guide. > > Go to the properties for the _CascadiaPackage_ project, choose Debug, and change the project type from "_Mixed (Managed and Native)_" to "_Native Only_". The `CascadiaPackage` can crash Visual Studio when the `Properties` (right-click) menu is selected. To fix the crash so VS can load Properties, select `x64` in the Platform dropdown. ![cascadiapackage-properties-fix](https://user-images.githubusercontent.com/48138103/78856594-2ef55580-79f5-11ea-9347-24135b854c3c.jpg)
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 Area-Build Issue-Bug Resolution-External
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#982
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?