-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
integratedTerminal not working anymore in V 1.2.1 #7000
Comments
There were no changes to vsdbg from v1.2.0 to v1.2.1 @sean-mcmanus There may be an issue either with the downloading of packages or the release setup. |
I don't know either. Nothing has changed with the release setup. Are we able to repro any of these regression issues? Do we know if the issue affects only the online vsix or also the offline vsix? |
I actually have the same problem but in another context: For me the Does this feature depend on a recent Windows 10 version? Is the Windows Terminal (from the Windows Store) required? How about the PowerShell version? Is currently hard to diagnose because we are all digital due to COVID but I scheduled a "real" meeting with one of my students tomorrow, maybe I can figure it out... |
All files will be bundled with the VSIX starting in 1.8.0. This should be covered by #8152 |
Type: Debugger
Debugging still works, but the
integratedTerminal
is not showing up again. If opening it manually, the output is not shown from the debugger.externalConsole
andinternalConsole
still are working.Describe the bug
To Reproduce
Checkout the code from here
Build using
nmake
or whatever compiler you like.Start debugging using the default debugger script in the
launch.json
Fix
Downgrade to
V1.2.0
still works.Note: If you downgrade, make sure you also disable the
Auto Extension Update
.The text was updated successfully, but these errors were encountered: