-
Notifications
You must be signed in to change notification settings - Fork 1.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not attempt post install ARP correlation if PackageFamilyName is provided and present for the user #3391
Merged
Merged
Changes from 7 commits
Commits
Show all changes
8 commits
Select commit
Hold shift + click to select a range
4d97bde
Needs E2E tests completed
JohnMcPMS d94d757
Finish test; comment out fix to ensure test fails without it
JohnMcPMS 06506a2
Remove fake ARP and force install
JohnMcPMS 5f0c24b
Merge from master
JohnMcPMS a5cafd4
Apply fix now that test has been shown to fail at appropriate location
JohnMcPMS 9ec8b25
const&
JohnMcPMS 838d0d7
Move tests to net6.0
JohnMcPMS 20739b1
Change directory in pipeline
JohnMcPMS File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
20 changes: 20 additions & 0 deletions
20
src/AppInstallerCLIE2ETests/TestData/Manifests/TestExeInstaller_InstallMSIX.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
Id: AppInstallerTest.TestExeInstallerInstallsMSIX | ||
Name: EXE Installer that Installs MSIX - extra | ||
Version: 1.0.0.0 | ||
Publisher: AppInstallerTest | ||
License: Test | ||
Installers: | ||
- Arch: x86 | ||
Url: https://localhost:5001/TestKit/AppInstallerTestExeInstaller/AppInstallerTestExeInstaller.exe | ||
Sha256: <EXEHASH> | ||
InstallerType: exe | ||
PackageFamilyName: 6c6338fe-41b7-46ca-8ba6-b5ad5312bb0e_8wekyb3d8bbwe | ||
Switches: | ||
Custom: /execustom | ||
SilentWithProgress: /exeswp | ||
Silent: /exesilent | ||
Interactive: /exeinteractive | ||
Language: /exeenus | ||
Log: /LogFile <LOGPATH> | ||
InstallLocation: /InstallDir <INSTALLPATH> | ||
ManifestVersion: 0.1.0 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
2 changes: 1 addition & 1 deletion
2
src/WinGetUtilInterop.UnitTests/WinGetUtilInterop.UnitTests.csproj
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this the intended way of doing the correlation? I thought that's what the AppsAndFeaturesEntries were for, so that the different InstallerType could be specified. In fact, this isn't the first time I've seen the issue where an exe installs MSIX packages -
If this is the intended way, that's great, I would only ask that it be documented somewhere that the PackageFamilyName may be used for correlation even though it is outside of the AppsAndFeaturesEntries, since based on the current manifest documentation, I would have thought that it wouldn't be used. And then, since the package behaves differently based on the OS Version, that there would be an installer node for each
MinimumOSVersion
that has a uniqueAppsAndFeaturesEntries
to make the correlation unambiguous.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
AppsAndFeaturesEntries
is for the Add/Remove Programs data in the Uninstall registry key. It doesn't contain the package family name:winget-cli/schemas/JSON/manifests/v1.5.0/manifest.singleton.1.5.0.json
Lines 568 to 600 in 531d2f1
Yes, the WinApp SDK / Runtime is what caused us to open that value up to installer types that were not definitely MSIX based. Where would you suggest that it be documented that
Installer > PackageFamilyName
be used when an MSIX is installed?The OS version targeting portion is relevant to the real manifest in question, not the test one. I don't think it should be necessary if we can help it though.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah, I see, that clarifies things. I think it can be documented at pkgs in the manifest docs; I can do that after this is merged.
Thank you for the explanation!