Repository navigation
Why is SixLabors.Fonts restricted to [1.0.0, 3.0.0) in Closed XML 0.105.1 #2892
visma-mrange
started this conversation in
General
Replies: 3 comments 1 reply
|
Version 3 introduced incompatible API changes and would throw exceptions.
…On Wed, Oct 14, 2026, 12:20 visma-mrange ***@***.***> wrote:
I am trying to upgrade to a new version of IronPDF. It uses
SixLabors.Fonts as is ClosedXML. However, IronPDF requires 3.2.0 but
ClosedXML is restricted to [1.0.0, 3.0.0) which creates a situation that
can't be cleanly resolved.
Is there a good reason why ClosedXML 0.105.1 has this restriction?
Regards,
mrange
—
Reply to this email directly, view it on GitHub
<#2892?email_source=notifications&email_token=AB2HZBCSA7J2M6C2QEQPPKT5T5HPBA5CNFSNUABBM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63RPGEYTAMJXGIYTJJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KYZTPN52GK4S7MNWGSY3L>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB2HZBB3GJHZIFDAQLWKXBL5T5HPBAVCNFSNUABHKJSXA33TNF2G64TZHM3DMNZQHEYDQOB3IRUXGY3VONZWS33OHMYTCMBRG4ZDCNFBOYBA>
.
Triage notifications, keep track of coding agent tasks and review pull
requests on the go with GitHub Mobile for iOS
<https://github.com/notifications/mobile/ios/AB2HZBDMFTVJ23XH4A4FSCD5T5HPBA5CNFSNUABBM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63RPGEYTAMJXGIYTJJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2KUZTPN52GK4S7NFXXG>
and Android
<https://github.com/notifications/mobile/android/AB2HZBBJXPFBMLD65L2XD3D5T5HPBA5CNFSNUABBM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63RPGEYTAMJXGIYTJJTSMVQXG33OVJZXKYTTMNZGSYTFMSSWK5TFNZ2K4ZTPN52GK4S7MFXGI4TPNFSA>.
Download it today!
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
1 reply
|
I'm running into the same issue. My workaround for now is implementing a custom "NoFontsGraphicEngine" and use it when I create a XLWorkbook. |
0 replies
|
Just to add some context on what I did. In our endpoint the point was to expose PDF Converter functionality. There was no way to reconcile the transitive dependency, either closedXML crashed or IronPDF crashed. So to make it work I had to drop ClosedXML dependency in that endpoint. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I am trying to upgrade to a new version of IronPDF. It uses SixLabors.Fonts as is ClosedXML. However, IronPDF requires 3.2.0 but ClosedXML is restricted to [1.0.0, 3.0.0) which creates a situation that can't be cleanly resolved.
Is there a good reason why ClosedXML 0.105.1 has this restriction?
Regards,
mrange
All reactions