Demitrius Nelon

I met with some of our PowerShell folks to learn more about how we should be documenting our modules. We will be using platyPS. It's going to take some time...

I took a first pass at the platyPS documentation. I'd like to get it merged in so the engineering team can work on the build pipeline steps to get it...

We're cutting a new build with the help files.

Microsoft.WinGet.Client with new help is out: https://www.powershellgallery.com/packages/Microsoft.WinGet.Client/1.9.2411 We need to tackle Microsoft.WinGet.Configuration and Microsoft.WinGet.DSC next.

The [help files](https://github.com/microsoft/winget-cli/tree/master/src/PowerShell/Help) are now included in the build. We still have plenty of work to improve the cmdlets and close gaps between the WinGet CLI, but I'm hoping this...

The new v2 schema has been deployed, and we've tested with several clients. This will be the default in the preview builds of WinGet 1.9.

This feature has been completed and is in the latest WinGet 1.8 stable version as well as WinGet 1.9-preview.

@upintheairsheep The Microsoft Store is designed to only distribute the latest versions of Apps across the matrix of supported OS and locale. If this changes, WinGet would have the ability...

@AliveDevil can you confirm if this was fixed in the WinGet 1.8 release?

@superBartimus We've been doing some work in WinGet with respect to packages that allow different versions to be installed side-by-side. If you are interested, you could try our latest preview...