Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
`dotnet run` doesn't handle ctrl-c well
See original GitHub issuePorting issue https://github.com/dotnet/corefx/issues/5339…
Even if the app being run has a CancelKeyPress handler, the SIGINT generated by typing ctrl-C goes to the dotnet run process, killing it.
Issue Analytics
- State:
- Created 8 years ago
- Reactions:17
- Comments:10 (6 by maintainers)
Top Results From Across the Web
How do I trap Ctrl+C (SIGINT) in a C# console app?
Here is how I solved this problem, and dealt with the user hitting the X as well as Ctrl-C. Notice the use of...
Read more >Handling CTRL-C in .NET Console Applications
By default, pressing CTRL-C while a console application is running will cause it to terminate. If we want to prevent this we can...
Read more >Run window's "Stop" Button does not properly emulate Ctrl+C
If I send CTRL+C in the Run window directly, the application catches the signal and begins to unload and exit properly, exiting with...
Read more >dotnet run command - .NET CLI
The dotnet run command provides a convenient option to run your application from the source code.
Read more >Graceful Shutdown C# Apps
I recently had a C# application that needed to gracefully shutdown a long-running process when the application is stopped by the user ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This seems pretty important to the
dotnet runexperience, has there been any update on this ticket or anywhere related?I wish I could do a +1 on the close status change here.