-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Open
Labels
area-setupInstallation, setup, requirements, maui-check, workloads, platform supportInstallation, setup, requirements, maui-check, workloads, platform supportarea-templatesProject templates, Item Templates for Blazor and MAUIProject templates, Item Templates for Blazor and MAUI
Description
When installing the unsuffixed dotnet new
templates:
dotnet new install Microsoft.Maui.Templates
…the package installed is Microsoft.Maui.Templates, which currently corresponds to the older v6 templates.
When installing the suffixed packages (e.g. Microsoft.Maui.Templates.net6
, Microsoft.Maui.Templates.net7
, Microsoft.Maui.Templates.net8
, Microsoft.Maui.Templates.net9
), the corresponding versioned templates are installed as expected.
Problem
This behavior feels unintuitive:
- Other template packages typically rely on the package’s semver rather than introducing suffixed names and essentially a new package.
- Keeping the default/unsuffixed template tied to an ancient v6 version doesn’t make sense, and can be confusing for new users.
Expected
The unsuffixed Microsoft.Maui.Templates
should point to the latest stable templates (currently net9), rather than being locked to v6.
Metadata
Metadata
Assignees
Labels
area-setupInstallation, setup, requirements, maui-check, workloads, platform supportInstallation, setup, requirements, maui-check, workloads, platform supportarea-templatesProject templates, Item Templates for Blazor and MAUIProject templates, Item Templates for Blazor and MAUI