Replies: 1 comment
-
Not 100% sure if this is the same thing as we ran into (since in our case it's in the MigraDocCore namespace, but I believe that's just the base for PdfSharp), but we simply worked around this by creating a duplicate of the ImageSource and setting it as the ImageSource static in MigraDoc: Anywhere during startup:
Then just use a reverse engineered class so you can use your own version of ImageSharp:
Hope this helps |
Beta Was this translation helpful? Give feedback.
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.
-
PdfSharpCore uses version 2 of ImageSharp. PdfSharpCore has not been updated for 6 month but will hopfully still keep working as long as SixLabors keep releasing new updates of version 2 of ImageSharp, and fixing vulnarabilities. Is there a date when version 2 no longer will be updated?
Beta Was this translation helpful? Give feedback.
All reactions