The Rider docs say the "Stop" button in the Run window emulates a CTRL+C signal, but that doesn't work as intended. I am using an IHostedService implementation with an IHostApplicationLifetime implementation using a registered Stopped method in ASPNET Core 3.0. If I send CTRL+C in the Run window directly, the application catches the signal and begins to unload and exit properly, exiting with an exit code of 0. If I press the "Stop" button, the application immediately halts, ignores the signal, and exits with a code of 1. I'm currently working on developing a server which requires a graceful shutdown as it deprovisions multiple out-of-band services when it's called to stop, so I'm relying on the implementation of the "Stop" button to be correct. Because it's not sending the proper key presses, my server is leaving lots of resources laying around. I've uploaded a video demonstrating the example. There's no PII data, so it's safe to be public. Version: RD-192.7317.11 Timezone: America/Denver Evaluation: false Environment:…