Update WinGet configuration file location & extension

[mdanish-kh]

Summary of the Pull Request

The new convention for WinGet configuration files if to place them in a .config directory with file extension .winget. See https://learn.microsoft.com/en-us/windows/package-manager/configuration/create#file-naming-convention

PR Checklist

• Closes: #
• Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
• Tests: Added/updated and all pass
• Localization: All end user facing strings can be localized
• Dev docs: Added/updated
• New binaries: Added on the required places
  • JSON for signing for new binaries
  • WXS for installer for new binaries and localization folder
  • YML for CI pipeline for new test projects
  • YML for signed pipeline
• Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

[denelon]

Related to:

• WinGet Configuration Updates #37636

[crutkas]

nice!

[crutkas]

can we move the .configurations into the .config folder?

[mdanish-kh]

@crutkas Are you suggesting a structure as .config/. configurations/<.winget files>? I'm not sure if that would be in line with the recommendation 🤔. @denelon Any thoughts?

[mdanish-kh]

My only concern would be if others start to adopt the powertoys way since it has been mentioned as a "reference repository" in quite a few places

[denelon]

I agree @mdanish-kh. The guidance is written as:

".config/configuration.winget" <- Default Configuration
".config/.winget" <- Other Configurations

It could be confusing to have the following since we no longer reference a ".configuration" directory.

"./config/.configurations/configuration.winget"

[crutkas]

I misread the paths, sorry, you did it correct

[denelon]

@mdanish-kh I'm not sure it should close the issue. I think there might still need to be changes in the configuration files to handle the securityContext: elevated. The configurations work when run elevated, but in user scope, I think enabling developer mode fails (but checking if it's in the right state works) due to lacking administrator privileges. I don't remember if installing Visual Studio requires elevation or not.

[mdanish-kh]

@denelon - I don't remember adding that bit in the description (looks like I'm right that I didn't 😆😆😄). Anyways, that makes sense & removed the closes issue ref

[yeelam-gordon]

Thanks to make it align with the practice of format

[crutkas]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).