Łukasz Kosson

What exactly is the point of targeting .NET 6 and newest C# version? There are also a few problems with this pull request: * Targeting .NET 6 requires VS2022 and...

Try setting .NET 6 on one project in this repo (for instance on `Microsoft.ReportViewer.Common`) and try to compile the solution. You'll get compilation errors on all the `ReportViewerCore.Sample.*` projects. On...

As far as I can tell - fresh .NET 6 project with nuget package `ReportViewerCore.NETCore` referenced and sources copied from `ReportViewerCore.Sample.Console` compiles and runs just fine.

I have published new packages (15.1.16) which provide separate DLLs for different .NET versions.

Hello. You might try putting Uniscribe DLLs from full Windows Server in your application directory in the container and see if it helps. As for now there are no workarounds...

Hi. Two weeks ago I've merged changes from LivingNaturally's fork, removing references to Win32-specific DLLs. Have you tried this version? If problem still occurs in most recent version, please check...

That does not look right. In LivingNaturally's fork DataProtectionLocal.LocalProtectData is an empty method. If you are compiling project from sources please inspect Microsoft.ReportViewer.Common\Microsoft.ReportingServices.Diagnostics\DataProtectionLocal.cs and check if LocalProtectData returns same blob...

For now there are no workarounds for PDF support on non-Windows platforms. It looks like PDFWriter uses native methods at least for computing glyph widths and other metrics. From earlier...

Directly from RV - not really. The best you can do is to print your report to Microsoft XPS Document Writer virtual printer.

PDF exporter depends heavily on font measurement functions provided by Windows Uniscribe DLLs and won't work on Linux or Mac OS. As of now, there is no workaround to get...