VS 2022. ASP.NET Core with Angular. Opening multiple ng serve consoles when ClientApp fails

[UseMuse]

Is there an existing issue for this?

• I have searched the existing issues

Is your feature request related to a problem? Please describe the problem.

When creating a new project on the "ASP.NET Core with Angular" in VS 2022 (Version 17.6.2), If there is an error in the ClientApp, when such a project is launched, then after a while an additional console will open with the following text

> [email protected] start
> ng serve --port 44425

? Port 44425 is already in use.
Would you like to use a different port? (Y/n)

What hinders the progress of development, because if there is an error, and I just could not quickly fix it, then in a few time you will have a lot of such pop-up consoles. Constantly covering it with your hands, annoying.

Describe the solution you'd like

One console. I suggest making this behavior manageable

Additional context

info: Microsoft.AspNetCore.SpaProxy.SpaProxyMiddleware[0]
      SPA proxy is not ready. Returning temporary landing page.
fail: Microsoft.AspNetCore.SpaProxy.SpaProxyLaunchManager[0]
      Unable to connect to the SPA development server at 'http://localhost:44425'.

[ghost]

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[ghost]

To learn more about what this message means, what to expect next, and how this issue will be handled you can read our Triage Process document.
We're moving this issue to the .NET 9 Planning milestone for future evaluation / consideration. Because it's not immediately obvious what is causing this behavior, we would like to keep this around to collect more feedback, which can later help us determine how to handle this. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact work.

[mkArtakMSFT]

Hi. Thanks for contacting us.
We're closing this issue as there was not much community interest in this ask for quite a while now.
You can learn more about our triage process and how we handle issues by reading our Triage Process writeup.