JohnMcPMS
JohnMcPMS
When fixed, re-enable the E2E test `InstallZipWithMsi`.
Since this is a portable and we fully control the version, why do we want to show `6.2.1` anyway? It is never going to work to have either the `PackageVersion`...
> I am concerned, however, that we don't have a good way for multiple "longer" versions to be supported with a single "marketing" version of a package. If we run...
> It probably changes a lot of the portable app implementation, but wouldn't that be better to do now before people have a bunch of apps installed with symlinks that...
I looked into the difference between these two builds and I don't see anything of consequence. The only files that changed were a mitigation to a crash that should not...
> We need to add support for filtering out updates by the OS on the client. That will resolve this issue. That won't resolve this particular issue, as I would...
I agree conceptually that it would be best to filter out versions when they are not applicable and support the state of no applicable versions. We could output `N/A` or...
This is an MSIX package in the Store, so you won't be able to install it as SYSTEM. We have had some discussions around implementing a machine scope install for...
The relevant C header is here: [WinGetUtil.h](https://github.com/microsoft/winget-cli/blob/master/src/WinGetUtil/WinGetUtil.h) The utils nuget package is not intended for public use, so there is not documentation beyond the code.
It is a native nuget package, so you would have to PInvoke these methods.