Visually unify the "Default Profile" and "Default Terminal" drop-downs

[pronichkin]

Description of the new feature

These two drop-downs follow the same pattern conceptually, but not visually. They should look similar.

• Should have the same width.
• Should have the same style. More specifically, the Default Profile should display the vendor and app version.
  • At very least, that should work for auto-generated profiled for well-known apps where we know for sure how to query those properties.
  • Bonus points if we could allow users to specify arbitrary provider name and version for the custom profiles they create manually.

Proposed technical implementation details

No response

[DHowett]

we know for sure how to query those properties.

every property we have to query from the app catalog is another, like, 100ms wasted on startup. It's awful. I'd rather not do any of it than add more version numbers (and figure out what that means for Command Prompt which is versioned as-Windows and Windows Powershell which is versioned as-???)

[DHowett]

Part of the reason we display it for the Default Terminal option is that users are configuring something with a systemwide impact, and they might like to know who published the thing that's going to take over all their console applications.

Profiles are much less impactful than that, and there is no true versioned registry of them... eh.

[pronichkin]

every property we have to query from the app catalog is another, like, 100ms wasted on startup.

so, don't do it on startup. Do it only if settings are opened at the page in question.

Part of the reason we display it for the Default Terminal option is that users are configuring something with a systemwide impact, and they might like to know who published the thing that's going to take over all their console applications.

debatable. The default profile impacts the same behavior that makes default terminal impactful. E.g., what version of PowerShell will open from the Explorer right-click menu, etc.

and there is no true versioned registry of them... eh.

that's why I'm saying let's at least do this for auto-generated profiles. Arguably, this will make a positive impact for 99% users. The remaining 1% who maintains their own profiles would know their stuff already.

(but even for them, perhaps, specifying the arbitrary version could be helpful. But that's just nice-to-have in my opinion.)

[pronichkin]

one more point I'd like to emphasize separately.

today, auto-generated profiles, there's no reliable way to tell which one is which judging solely by the name, if you have multiple versions of the same shell installed. E.g., on one machine it's called PowerShell (msix) while on another machine it's called PowerShell (preview). Yes, there is logic behind how these names get generated. But from a casual user perspective, that's almost non-deterministic.

so, you have to first go to the list of profiles, take a note of what's the current name of the profile you want, then head back to the page with default profiles to make the selection.

it would be much more straightforward if we had versions right there, in the drop-down list.