develop a SSRS ReportViewer for ASP.NET Core
Develop a SSRS ReportViewer for ASP.NET Core
VA Chris
shared this idea
186 comments
-
Joshua Matthews
commented
No way there isn't a report viewer for .net 5 right?
-
Abdul Hannan
commented
Desperately need this
-
Anonymous
commented
I'm so shocked. Just started migrating our backoffice solution to .Net Core only to discover we can't use our 100+ SSRS reports in .net core 5.0!
What a shambles.
C'mon M$, we need this or we'll have to use someone else's reporting server.
-
Alex
commented
Desperately need this
-
Anonymous
commented
please
-
Anonymous
commented
Is there a legal battle behind this, or just poor planning?
Reports area has been painful with Microsoft since times of Crystal Reports when it was removed from VS, nowadays we are still following Microsoft programming and reporting technologies and we end up abandoned when trying to put applications in ASP.NET Core MVC and reports SSRS together.
Please provide some feedback to continue managing your technology in our companies or we might end up with good reasons to migrate to other technologies.
Thank you.
-
Anonymous
commented
So we are at .NET 5 now, and still no progress at all?
-
HOVE
commented
Does anyone know how to render rdlc reports to PDF in .NET Core? AspNetCore.Reporting doesn't support subreports.
-
Martin Dye
commented
MS could potentially use Blazor or a razor component.
Aside from that, there needs to be an upgrade path from .Net Fwk > .Net Core with regards to Microsoft.ReportingServices.ReportViewerControl. -
Paulo Borges
commented
I'm Waiting for this for long time, but we can stop because Microsoft not provide solution.
A have split the solution in 3 Application (UI, REST, REPORT)
1) UI application on ASP.NET Core with razor (target net5)
2) REST application ASP.NET (target net5) running domain/rest
3) Just reporting ASP.NET 5 (target net4.8)
x) Reverse proxy Configured for example.com/ui, example.com/rest example/report
z) Authentication with JWTFor the user point of view is just one site to go.
-
hiren patel
commented
i can't understand where this client side javascripting/ razor/ js is fast
false propaganda will lead.gradually server side development is dying but like phinix it will come alive one day...
-
Roland Mai
commented
In all my complex applications for enterprise, there are SSRS reports embedded with in the application. It's quite amazing that 4 years later there is no solution for this.
Is Microsoft being lead by the cool kids who think reports are sooooo pase?!
-
Nestor Rojas
commented
Anyone has a good working example as per Jason suggestion, having a separate app running webforms? I am trying to get this done calling from cshtml razor view
-
Italo
commented
Yes, please. I have a new ASP.NET Core application. Also angular. Looking how to show users a report (SSRS ReportViewer) without them having to login twice. Researching workarounds to see if it is better to show old WebForms page or create a new MVC page. Either way it is going to look different than the angular UI which are all the other pages in this app.
-
Jason
commented
My only suggestion to anyone currently stuck with this problem is to consider running a .Net4.7 webforms report viewer in a separate application and then in MVC use ProxyKit to proxy your MVC requests using middleware to the actual report viewer.
-
Anonymous
commented
Getting stuck with and by Microsoft!! If I need to stay on framework then microsoft should fix the nonce issue owin package while upgrading to AAD authentication. If not, provide a solution to embed SSRS in .net core so that AAD issues and SSRS issues can overcome!!
-
Russel Rillema
commented
Do we know if the ReportViewer will be supported in .NET 5?
Also will this ReportViewer, if picked up, replace the report viewer in Microsoft.Reporting.WinForms? I.e., will I be able to stitch together multiple RDLCs using memory stream to generate my report?
-
Brian
commented
Microsoft? What is status of this? Please be more transparent.
-
Andrew Allan
commented
Please add this
-
Anonymous
commented
Yes, Please, it's time to get this feature added to .netcore3.1