Update New-ExternalHelpCab to build large cab file #497
Conversation
This file contains hidden or 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
SteveL-MSFT
approved these changes
Jan 11, 2021
- Fix build error updating help - Fix appveyor script - Pin Pester to version 4.10.1 - update module list - Fix or comment out failing tests
SteveL-MSFT
requested changes
Jan 12, 2021
SteveL-MSFT
approved these changes
Jan 12, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
PlatyPS users MakeCab.exe to create the cab files. By default CAB files are limited to the size of a floppy disk (1.44M). When that size is exceeded, MakeCab create additional CAB files until all files are compressed. PlatyPS only expects a single CAB file.
The SCCM ConfigurationManager module is hitting this size limit. This causes Update-Help to fail because only the first CAB is published.
This change should bump the CAB file size limit to ~600MB.
I have locally tested this change with the SCCM content.
@SteveL-MSFT @theJasonHelmick