Kaleb Luedtke
Kaleb Luedtke
> @Trenly I'm not sure how this will conflict it If a user were to type `winget upgrade Microsoft` - there are multiple packages that match. The conflict would be...
@denelon - I would argue that this is `Issue-Feature` and not `Issue-Bug`. The current behavior of `-q` for `install`, `show`, and `upgrade` is that it is a single-package operation, and...
Is this possibly related to https://github.com/microsoft/winget-cli/issues/2498 ?
> For adding support of a new type, it'd be better to add the basic install, upgrade, uninstall workflow tests in Workflow.cpp in unit tests to exercise the whole flow,...
> Regarding unit tests, they should be added to WorkFlow.cpp under AppInstallerCliTests peoject, the project builds as an exe, you can just run the exe to run the tests. For...
> Advanced Installer returns the same exit code as MSI's except -1 and 1, according to https://www.advancedinstaller.com/user-guide/exe-setup-file.html. I must have missed that; Will update
> Azure Pipelines successfully started running 1 pipeline(s). I cri. For some reason it won't let me run the tests locally, seems like its related to my setup though. It's...
> > Would you be able to help me identify where the error is? > > The pipeline shows 10 tests failed, some seems not directly related to this change....
> > Edit: I'd like to rebase this on master first to ensure the additional expected return codes can be used > > Sure, thanks Rebased and pushed
> /azp run Thank you, I think I see why it was erroring now with the commits you added