[AspireE2E] After installing Aspire 9.3, the default aspire version selected during project creation is still 9.2 instead of 9.3 for web projects using .NET Aspire orchestration.

[vmykagapuz]

REGRESSION

1. Worked in Aspire 9.2.1

INSTALL STEPS

1. Clean machine: Win11 x64 24h2 ENU
2. Install VS 17.14
3. Install the latest Aspire 9.3.0
   - dotnet new install Aspire.ProjectTemplates::9.3.0 --force

NOTES

1. This issue does not reproduce when creating .NET Aspire templates.

REPRO STEPS

1. Open VS > New Project > ASP.NET Core Web App (Razor Pages) > .NET 8.0/9.0 framework > Check 'Enlist in .NET Aspire orchestration

ACTUAL
The default Aspire version selected during project creation is still 9.2 instead of 9.3

EXPECTED
The default aspire version should be 9.3

[maddymontaquila]

@DamianEdwards thoughts on this?

[DamianEdwards]

The version is currently configured to be "sticky" in the templates, so the last version you selected is the default. We can change that so it's always the latest instead.

[v-elenafeng]

The version is currently configured to be "sticky" in the templates, so the last version you selected is the default. We can change that so it's always the latest instead.

In VS it does stick to the last selected version, not just for aspire. But the issue reported here is that the default Aspire version when first creating a web application is not the latest version, but for an Aspire application it is.

[DamianEdwards]

@v-elenafeng ahh thanks for the clarification. @phenning is this on your side then?

[phenning]

Interesting, it looks like we are just grabbing the first version in the list, when it was 9.1 and 9.2, 9.2 was first in the list, with 9.2 and 9.3, for some reason, 9.2 is in the list. Note that this is NOT sticky when adding the orchestration, but we always default to the first version in the dropdown currently.

@DamianEdwards did you want this to be sticky, or would you prefer to automatically select the highest installed version always when there is not an existing apphost in the solution, and just fix the logic so the highest version is listed first? Note that we only display the picker in the case where there is no AppHost present?

[DamianEdwards]

did you want this to be sticky

I think it's fine to default to highest here. We're considering removing the stickiness from our templates for the version anyway.

[maddymontaquila]

Agree wth @DamianEdwards - default to highest/latest! Thanks @phenning !