Add native support for .cab, .msix and .msixbundle installer types
- Dominant language
- C#
- Stars
- 11.5k
- Forks
- 960
- PR merge metrics
- No merged PRs in 30d
Description
### Checklist
- [x] I have verified this is the correct repository for opening this issue.
- [x] I have verified no other issues exist related to my request.
### Is Your Feature Request Related To A Problem? Please describe.
When creating packages that contain a `.cab` or `.msixbundle` file, the work of installing the files needs to be done in the script. Chocolatey CLI has support for natively installing other file types, which makes that work unnecessary for those file types.
### Describe The Solution. Why is it needed?
Add support for `.cab` and `.msixbundle` file types so that that packages can be created with `choco new` and they can be installed using the traditional `Install-ChocolateyPackage` and `Install-ChocolateyInstallPackage` functions / cmdlets.
### Additional Context
* This was suggested by a customer during a call.
### Related Issues
_No response_
* [ ] [MSIX](https://learn.microsoft.com/en-us/windows/msix/overview)
* [ ] Microsoft Cabinet files (.CAB)
* [ ] Bundle of MSIX files (.MSIXBUNDLE)
* [x] Microsoft Patch files (.MSP) (already [added](https://github.com/chocolatey/choco/pull/2113))
* [x] Microsoft Update files (.MSU)
Contributor guide
Research direction
Start by tracing the existing native Microsoft Patch (.MSP) and Microsoft Update (.MSU) support referenced in the issue, then inspect the choco new flow and the Install-ChocolateyPackage and Install-ChocolateyInstallPackage entry points. Done means packages containing .cab, .msix, and .msixbundle files can be created and installed through those native paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli, devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100