[Bug] Missing Extensions Options in UnoFeatures starting from Blank Preset when creating projects with Uno Templates, VS Wizard, or Live Wizard

[agneszitte]

Description:

I'm encountering an issue with the latest Uno templates (v5.4.5) and the latest VS Uno Extension (v5.4.11) with Wizard when attempting to add various extensions options to a blank preset project. The issue affects not just Localization, but other extension options such as HTTP as well, which do not get properly reflected in the <UnoFeatures /> in the .csproj of the project. Below are the details with the Localization option as an example :

Steps to Reproduce:

Using Visual Studio Wizard:

1. Select a Blank Preset project.

2. Enable Dependency Injection (DI) and Localization.

3. Create the project.

4. Observed Behavior: The corresponding entry Localization is missing from UnoFeatures in the .csproj file of the project.

   MissingLocalizationUnoFeatureWizard.mp4

Using Live Wizard:

1. Select a Blank Preset project.

2. Enable Dependency Injection (DI) and Localization.

3. At the end, notice that option -loc is missing from the generated command.

4. Copy and paste the command to manually create the project.

5. Observed Behavior: Obviously, no corresponding entry Localization in UnoFeatures in the .csproj file of the project.

   MissingLocalizationUnoFeatureLiveWizard.mp4

Using CLI:

1. Use the blank preset command (dotnet new unoapp -preset=blank -o test) and manually add -di and the localization option -loc.

2. Observed Behavior: The corresponding entry Localization is missing from UnoFeatures in the .csproj file of the project.

   MissingLocalizationUnoFeatureCli.mp4

Additional Observations:

• Additional Live Wizard Tests:
  • Blank preset + DI produces a correct command.

Warning

Adding extensions such as Configuration or HTTP or Localization after selecting DI does not update the command at all, meaning that these options are not included in the generated project.

Live.Wizard.command.Issues.mp4

Expected Behavior:

In all cases, when selecting additional extensions such as Localization, Configuration, or HTTP, these options should be properly reflected in the UnoFeatures of the .csproj file and the generated command (for Live Wizard).

[agneszitte]

• It needs to be verified whether this is a regression or if it's been present for a while but went unnoticed.
• We also need to check if this issue occurs in other sections outside of Extensions.

cc @jhanvi03, @Darsh0307

[agneszitte]

Are we missing any additional tests? (cc @nickrandolph for info)

From @jeromelaban:

If we do not have such validations in the uno.templates generation, we need to add some more.