PDFsharp & MigraDoc Foundation

Hello,

Thank you for this very useful software.

I have a Blazor project targetting .Net6.0 which builds and works ok.
However, I get this warning:

NU1701 Package 'PDFsharp 1.50.5147' was restored using '.NETFramework,Version=v4.6.1, .NETFramework,Version=v4.6.2, .NETFramework,Version=v4.7, .NETFramework,Version=v4.7.1, .NETFramework,Version=v4.7.2, .NETFramework,Version=v4.8, .NETFramework,Version=v4.8.1' instead of the project target framework 'net6.0'. This package may not be fully compatible with your project.

Also, when I change XFontStyle to XFontStyleEx, the code does not compile. There is no reference to .Net Framework in the csproj file e.g.
<TargetFramework>net6.0</TargetFramework>
...
<PackageReference Include="PdfSharp" Version="1.50.5147" />

I believe I am using the latest version of PdfSharp from empira. I have not tried "PdfSharpCore" from Stefan Steiger as I assumed it was something quite different and irrelevant to this problem.

Thanks for any guidance with this,

James.

When using PDFsharp 6.0.0-preview-2 (the latest published version by empira), you have to use XFontStyleEx. This version of PDFsharp targets .NET 6.

When using PDFsharp 1.50, you have to use XFontStyle. This version of PDFsharp targets .NET Framework 3.5.
You are still using PDFsharp 1.50.

Check "Include Prereleases" and switch to PDFsharp 6.0.0-preview-2.

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

Terrific - thanks!
I hadn't appreciated the 'prerelease' part and now have 6.0.0.0-preview-2 installed with no problems. [I have yet to run the application, but don't expect problems.]

Thanks again for the quick repsponse,

James.

Hi, I just want to note that document rendering fails in Blazor WASM project due to creation of the ILoggerFactory singleton instance.
You can work around this by assigning the singleton to your own instance before using the library: