You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes the compiler output is useful in troubleshooting issues with an analyzer (i.e. a missing dependency or some other error that prevents hitting breakpoints in the analyer itself).
When debugging, there's no way to prevent the launched csc from closing right after it finishes, making inspecting its output impossible.
Sometimes the compiler output is useful in troubleshooting issues with an analyzer (i.e. a missing dependency or some other error that prevents hitting breakpoints in the analyer itself).
When debugging, there's no way to prevent the launched csc from closing right after it finishes, making inspecting its output impossible.
I also tried the following without success:
NOTE: the debugger component does not honor the IDE setting to not close the console when debugging stops either:
The text was updated successfully, but these errors were encountered: