There's some difference in how VS launches Aspire projects launch compared with how it launches regular ASP.NET Core projects, e.g., Blazor Web ones.
With a default Blazor project, and assuming you have hot reload enabled, each time you ctrl+f5, VS will reuse the same browser tab if you have one open. With Aspire, each time you ctrl+f5 it opens a new tab for the dashboard, which leads to continually closing duplicate tabs.
There's some difference in how VS launches Aspire projects launch compared with how it launches regular ASP.NET Core projects, e.g., Blazor Web ones.
With a default Blazor project, and assuming you have hot reload enabled, each time you ctrl+f5, VS will reuse the same browser tab if you have one open. With Aspire, each time you ctrl+f5 it opens a new tab for the dashboard, which leads to continually closing duplicate tabs.
Or is this just on my machine?