vscode-aspire-postdebug-cleanup

To clean up orphaned .NET Aspire processes, you can configure a postDebugTask in your VS Code launch.json to automatically run a script that terminates lingering DCP and dashboard processes and stops associated Docker containers.

.NET Aspire processes and Docker containers can be left orphaned when the VS Code debugger stops unexpectedly, preventing graceful shutdown and causing system clutter, port conflicts, and resource exhaustion in your local development environment.

Automatically stop Aspire Docker containers by linking a cleanup script to the postDebugTask in your launch.json, which executes upon debug termination to stop and remove containers tagged with specific Aspire resource labels.

The best way to prevent port conflicts from leftover .NET Aspire processes is automating their termination via a post-debug script that targets specific PIDs and removes associated Docker containers, ensuring a clean environment for the next run.

Yes, the Aspire post-debug cleanup script requires shell execution permissions and standard Unix utilities like ps, kill, and docker to identify and terminate orphaned processes and containers effectively.

Yes, you can manually execute the cleanup script to terminate orphaned .NET Aspire processes and Docker containers, though configuring it as a postDebugTask in launch.json automates the process whenever a debugging session ends.