-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Caching Issue when there are multiple RDLC files #9
Comments
You are the same situation as me |
Hi @binypsw, so yeah I managed to resolve this by moving the report generation part to a .NET core console app. From the api i start the console app as a separate process. For each report the process starts and generate the report. I create all the data from the api save it as a json file and call the console app process. It will read the data from the saved json file and generate the report and save it. API will retrieve the generated file. You can use a guid to map the report and data files. This adds a delay to the report generating process. However it solved the issue as every time the process finishes the memory will be destroyed. Because we can't resolve the caching issue which is an internal issue in the library. |
I resolve it by move all parameter to dataset. It work. Dont use parameter
is answer for me
On Mon, 6 Apr 2563 at 07:41 tharindubuddhi ***@***.***> wrote:
You are the same situation as me
Can you fix it already?
Hi @binypsw <https://github.com/binypsw>, so yeah I managed to resolve
this by moving the report generation part to a .NET core console app. From
the api i start the console app as a separate process. For each report the
process starts and generate the report. I create all the data from the api
save it as a json file and call the console app process. It will read the
data from the saved json file and generate the report and save it. API will
retrieve the generated file. You can use a guid to map the report and data
files. This adds a delay to the report generating process. However it
solved the issue as every time the process finishes the memory will be
destroyed. Because we can't resolve the caching issue which is an internal
issue in the library.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#9 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADLKB6SMDYNG4YDRPHLLEQLRLEQK7ANCNFSM4ITZSOAQ>
.
--
*Bin Yiengprugsawan*
Electronic Government Agency(Public)
Software Engineer
108 Bangkok Thai Tower Building Rangnam Rd.,
Phayathai, Rachathevi, Bangkok 10400, Thailand
Tel. 026126000 - 5108
bin.yiengprugsawan.ega.or.th
|
Hello
As Of your suggestion i have implemented but till now i am getting same issues. i have multiple rdlc report in .net core application so caching issues. so can you suggest more. |
I also have the same issue. Any help? |
You can also use This nuget package to execute your report generation function in separate process. |
@Akash-JS but how do you read response from it (e.g. ReportResult from LocalReport.Execute()) |
This is something which is already explained by @tharindubuddhi , though I am providing a WORKING EXAMPLE here. Prerequisite - newtonsoft nuget, Tmds.ExecFunction nuget
With the help of above code you can also include some conditions at the level of RDLC file path generation and achieve multiple RDLC execution. |
@Akash-JS thanks for the response and detailed example! Meanwhile, I've managed to get it work by using console app for generating reports (a new process) and named pipes for interprocess communication (to avoid writing / reading from file overhead). |
FunctionExecutor.Run code is not running. Missing any reference or something like that in the example that you put? Thank you. |
Something at Program.cs? |
I also have this issue can the author plz work on it. Thanks |
@binypsw Could you show me an example of how you achieved that, because it not working with me? |
Hello. |
I resolve it by move all parameter to dataset. It work. Don't use parameter all report is answer for me |
How did you solve this problem? I have the same |
How did you do |
Forget about it, problems will never be fixed. The solution is here: https://www.nuget.org/packages/ReportViewerCore.NETCore/ |
@UrosBgd can u please help with sample code. How did u manage to solve the problem |
But how to Pass Multiple Parameters to Report |
Here is my Code: DataTable dt = new DataTable(); LocalReport report = new LocalReport(Path); Dictionary<string, string> param = new Dictionary<string, string>(); var result = report.Execute(RenderType.Pdf, 1, param); How i can Pass my parameters to FunctionExecutor. |
Hello, pdf file not found exception, |
Hi,
This library saved lot of my problems initially and it worked fine when I had only one report file.
The issue came when there are multiple rdlc files in the system. I'm generating the report using asp.net core API. Every time the api restarted the first called report will work fine. And the second one does not work or the second one mix content with the first one. When we restart the api and start from the second report it works but not the first.
I'm assuming this a caching issue.
It would be great if you can fix this issue.
Regards,
Tharindu
The text was updated successfully, but these errors were encountered: