In past versions of .Net Framework ASP.Net Zero implementations we have used Reporting Services to populate an RDL and push out to browser as PDF. We are implementing the .Net Core version of ASP.Net Zero and cannot find the proper method for implementing this feature to move our code forward.
Since MS is not moving Reporting into .Net Core I am left to assume their recent acquisition from Forerunner Software will be their path forward. That technology will likely take another year or so to mature.
My intuition is leading me to build a separate "service" that can run on the server and respond to requests to bind data to RDLs. This service could be told to emit a PDF back into our file system or document management system and create an abp "alert" for the original user that requested the report. They in turn would go into the "Document Management" portion of the Asp.Net Zero app and download it. In addition to that we could use the same tool to "bulk" process hundreds of RDLs (Invoices) offline and parallelize the app for performance leaving the Asp.Net Zero app free to service the users and UI.
Has anyone else tackled this ?
1 Answer(s)
-
0
Hi @HCCNOV,
If Reporting Services doesn't provide .NET Core support at the moment, your approach seems a good way to overcome this problem. If you have any AspNet Zero relataed question, we will be happy to help you.
Maybe other developers can share their experience about this as well.
