Łukasz Kosson

Most likely you get an error page from web server instead of a proper RS response. Inspect the response body and server logs to see what's wrong.

I can't reproduce the behavior in a sample project. Changing `Price` column format specifier to `P1` produces properly formatted percentage with one decimal digit - both in PDF, XLS and...

Right - adding decimal places to the `Price` triggers the behavior. However, the same problem occurs in original Report Viewer when exporting to Excel. It is caused by `Microsoft.ReportingServices.Rendering.ExcelRenderer.SPBIF.ExcelCallbacks.Convert.FormatHandler.GetLongNumberFormat`, which...

Please provide a sample project based on `ReportViewerCore.Sample.WinForms` from this repo reproducing the behavior.

No idea, but if it works in original RV, it should work here too.

This issue seems unrelated to #101. As far as I can tell, custom code and expressions work mostly fine on Linux.

Hello, Please provide a full stack trace of the exception. I know little about Blazor, but chances of RV compiled to WebAssembly working are slim; most likely limited to HTML,...

Most likely ReportViewer won't work in Blazor. While the error you've encountered can be fixed (call to Process.GetCurrentProcess() can be removed or guarded when running in Blazor), report compilation using...

Apart from bypassing `Process.GetCurrentProcess()`, Blazor support requires changes to `ExprHostCompiler` and `VBExpressionCodeProvider` to pass runtime and user DLL references to Roslyn compiler in a way that is mutually exclusive with...

Which functionality from the original Report Viewer are you refereing to?