Dev Home extensions do not have a configuration friendly name

[acangialosi]

Dev Home version

0.1701.597.0

Windows build number

10.0.22631.4112

Other software

OS Build Version: 10.0.22631.4112.amd64fre.ni_release.220506-1250
.NET Version: .NET 8.0.7

Steps to reproduce the bug

Open a terminal prompt
Run winget search "dev home"

Expected result

No response

Actual result

Result all of the Dev home extension have a random alphanumeric value for their ID.
Dev Home is supposed to encourage config as code setup of an environment. Installing Dev Home and the related extensions are a critical part of that process. These extensions should have a "Microsoft.*" friendly ID for users to enter into their DSC configurations rather than the alpha numeric values used today.

Included System Information

CPU: Intel(R) Core(TM) Ultra 7 165H
Physical Memory: 31.64GB (18.38GB free)
Processor Architecture: x64

Included Extensions Information

Extensions:
Microsoft.Windows.DevHome_0.1701.597.0_x64__8wekyb3d8bbwe (Core Widget Extension)
Microsoft.Windows.DevHome_0.1701.597.0_x64__8wekyb3d8bbwe (Hyper-V Extension)
Microsoft.Windows.DevHome_0.1701.597.0_x64__8wekyb3d8bbwe (Windows Subsystem for Linux Extension)
Microsoft.Windows.DevHome_0.1701.597.0_x64__8wekyb3d8bbwe (Git)
Microsoft.Windows.DevHomeGitHubExtension_0.1700.597.0_x64__8wekyb3d8bbwe (Dev Home GitHub Extension (Preview))
Microsoft.Windows.DevHomeAzureExtension_0.1200.597.0_x64__8wekyb3d8bbwe (Dev Home Azure Extension (Preview))

Widget Service:
MicrosoftWindows.Client.WebExperience_524.18500.10.0_x64__cw5n1h2txyewy

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it. Thank you!

Open similar issues:

• Address Microsoft Dev Box discoverability issues in Dev Home (#3593), similarity score: 0.79

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

[denelon]

Thanks @acangialosi for calling this out and creating an issue. The "Package Id" values are coming from WinGet's "msstore" source. I agree they are hard to reason about without doing a search or some other form of prior knowledge. I'll bring this up to the team responsible for these identifiers to see if we can get some traction on some kind of process to generate "human readable / friendly" package identifiers.