Follow-up improvements to Aspire 9 debugging and configuration

[tjementum]

Summary & Motivation

Aspire is now configured to keep SQL Server alive between debug sessions using the new Aspire 9 .WithLifetime(ContainerLifetime.Persistent), significantly improving secondary startup.

Unfortunately, Aspire does not seem to release ports immediately upon shutdown, requiring 10 seconds to a minute before the AppHost can restart. To mitigate this issue temporarily, logic has been added to kill any Developer Control Pane processes (dcpctrl) from previous sessions when starting the AppHost, preventing conflicts and strange errors. For more details, see this issue: https://github.com/dotnet/aspire/issues/6704.

The SPA generation and index.html caching strategy have been updated to align with the new Aspire startup behavior during debugging.

The AppGateway no longer launches automatically when starting Aspire AppHost, as it needs a moment to be ready.

Additionally, a bug has been resolved where the frontend incorrectly used the old platformplatform.pfx certificate instead of localhost.pfx.

Lastly, a fix for a duplicated dotnet dotnet issue in the README has been applied.

Checklist

• [x] I have added a Label to the pull-request
• [x] I have added tests, and done manual regression tests
• [x] I have updated the documentation, if necessary

[linear[bot]]

PP-257 Optimize Aspire configuration after upgrade to Aspire 9

[sonarcloud[bot]]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud