Updating guidance for naming configuration files

[denelon]

The current guidance at https://learn.microsoft.com/windows/package-manager/configuration/create#file-naming-convention is going to be updated.

We're going to recommend using the ".winget" file extension now that we have a handler so users can experience a "double-click" launch. Visual Studio code now treats files with this extension as YAML so IntelliSense can be enabled with the YAML plugin.

I've seen a few opinions about where to put the files.

Some folks have suggested ".config" as the directory for the default configuration.

I don't know if this is going to cause any negative impact. I'd also like to see if folks have strong opinions about another directory.

In some cases, there may be a need to have more than one configuration. Are there any opinions about going with "configuration.winget" or "default.winget" for the default configuration, or does it make more sense to just let projects specify the names the way they want? For example, PowerToys has configurations for the different Visual Studio SKUs.

The goal is to make it easy for new contributors to projects. Contributors should be able to clone the repository on their local device and then run winget configure <foo>.winget or simply double-click the file to install dependencies and configure the system so they can get to the business of writing code.

[Gijsreyn]

Should configuration parameters also be taken into account @denelon? Especially with v3 experimental around the corner.

[denelon]

We have been in lots of productive discussions with the PowerShell team jointly looking at DSC v3. I'm expecting with the experimental feature, all the capabilities offered by DSC.exe to be available for WinGet. We will have to reason over the best way to handle parameters as well.

[Gijsreyn]

Yes, cool! I wanted to add it so it is not forgotten. If I get some time, I'll try to think along because I like to see some standardization on naming conventions also :)