PDFsharp & MigraDoc Foundation

Hello,

I have upgraded to PDFsharp 6.1.1 by adding it to my project using NuGet. I am running Visual Studio 2022 Community and have also upgraded to dotnet 8.0.402.
Since doing this my project can no longer create a pdf. I have modified my code to correct the older xFontStyle to xFontStyleEx etc., but now I get an error when I try:

I get error:
System .IO.File Load Exception. It says "Could not load file or assembly:"
"Microsoft.Logging.Abstactions, Version 8.0.0.1, Culture = neutral, PublicTokenKey = .......

Searching for this has led me to a concern that I should have have downloaded assets as per the "Prerequisites page:" https://docs.pdfsharp.net/General/Overview/Download-Assets.html.
Does adding from NuGet still require this Prerequisite download of the assets? Or is this a separate issue altogether?

Thank you for you assistance.
Brad

The NuGet package has a dependency on Microsoft.Extensions.Logging.

Please add https://www.nuget.org/packages/Microsof ... ions/8.0.1 to your project and let us know if that resolves the issue.

_________________
Best regards
Thomas
(Freelance Software Developer with several years of MigraDoc/PDFsharp experience)

Thanks Thomas
That did the trick.
With the upgrade to 6.1.1 I am also receiving many warning about conflicts:
"System Memory"
"Microsoft.Bcl.AsyncInterfaces"
"Microsoft.Extensions.Options"
"Microsoft.Extensions.DependencyInjection"
"System.Diagnostics.DiagnosticSource"

Is this related to the upgrade and is it possible to remove these warnings?

Thanks again
Brad

Find out which NuGet packages use older versions of these packages and try to upgrade those.
Can be difficult to find which packages bring references to old packages with them, but can be done.
We switched from the 6.0 logging version to the 8.0 logging version to remove warnings about the System.Memory module.

_________________
Best regards
Thomas
(Freelance Software Developer with several years of MigraDoc/PDFsharp experience)

Thanks Thomas
I did find upgrades available for Logging to 8.0 and processed those, however the warning still persist. Will keep looking.

Thanks again
Brad