Demitrius Nelon

We're using this [discussion](https://github.com/microsoft/winget-cli/discussions/2361) to track business requirements for Windows Server support.

@turpie, The export command is designed to produce a JSON file used by the import command. We've got features to add support for additional information for the import command. We're...

Does this argument work with any command? Does it display the help across all commands? Maybe a quick spec would make sense for this one. I'm expecting we need to...

Maybe it should be an experimental argument initially then. It allows us to get feedback before releasing it with the GA client if we need to iterate.

Yes, I agree we should cover the other types of arguments as well as they relate to PowerShell.

There may be cases where a subsequent install is intentional. A user might be attempting a downgrade scenario. We might also prompt "Did you want to upgrade?" or something like...

We should notify the user that the package is already installed and inform them it's possible to use "upgrade". We will still likely keep the `--force` option for install, and...

How about: The current version is installed on the system: ``` >winget install "visual studio code" Warning: Microsoft Visual Studio Code [Microsoft.VisualStudioCode] is already installed. No upgrade is available. >...

We could have three settings "automatic-upgrade", "inform-only", and "prompt" which could give a [Y] | [N] option for the upgrade. Note this would also be impacted by the future work...

It is possible to get the "file version" from an .exe, but that doesn't always correlate to the registry entries that are used to display package versions in Windows Apps...