Bump LargeXlsx to 2.0.1 and remove useZip64 option#921
Merged
albertospelta merged 2 commits intomainfrom Mar 2, 2026
Merged
Conversation
The export library (LargeXlsx) dropped its SharpCompress dependency and now uses System.IO.Compression. SharpCompress did not fully support Zip64 and could produce corrupted Excel/LibreOffice files.
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This pull request updates the Excel export functionality to remove the experimental Zip64 feature and instead use the new compression API provided by the
LargeXlsxlibrary. It also upgrades theLargeXlsxpackage to version 2.0.1, which introduces this new API. The changes simplify the export code and remove user-facing controls for enabling Zip64.Excel Export Refactor and Library Update:
Excel Export Implementation:
Removed the
useZip64parameter from allExportExcelFilemethods and their implementations, eliminating the user option to enable Zip64 compression. The code now always uses the newcompressionLevelAPI (XlsxCompressionLevel.Fastest) for file writing. [1] [2] [3] [4] [5] [6] [7]Removed all code and diagnostics related to the Zip64 experimental feature, and the logic for enabling it via keyboard shortcuts in the controller. [1] [2] [3]
Library Upgrade:
LargeXlsxNuGet package from version 1.10.0 to 2.0.1 inBravo.csprojto support the new compression API and remove Zip64 dependencies.