Skip to content
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

Asp.Net Core Reporting (SSRS) #1528

Closed
KerolosMalak opened this issue Jun 2, 2016 · 269 comments
Closed

Asp.Net Core Reporting (SSRS) #1528

KerolosMalak opened this issue Jun 2, 2016 · 269 comments
Labels
External This is an issue in a component not contained in this repository. It is open for tracking purposes.
Milestone

Comments

@KerolosMalak
Copy link

I am working on ASP.NET Core app and cannot find a solution for displaying SSRS reports. With the absents of "Microsoft.Reporting.WebForm" no longer works. What is the best practice for displaying SSRS reports on the web in ASP.NET Core

@MaximRouiller
Copy link

With Core still being in RC (RTM by the end of the month), I don't think that an SSRS scenario is planned within the next 6 months but I'm not part of the team.

I would either generate those reports on the client side by using some javascript libraries or pre-generate those reports.

If you need something more "integrated", you can check out this community package:

https://github.com/ilich/MvcReportViewer

By the look of the issue ilich/MvcReportViewer#121, they are interested in integrating it but with no success thus far.

@mmgafri
Copy link

mmgafri commented Jun 6, 2016

I don't understand why the dotnet and ASP.net core initiatives are keeping silent on this issue on all previous announcements. It is like
[Reporting is not a major concern for developers and they can deal with it using html and print css classes]
currently we are migrating a small erp with alot of ssrs rdlc files and css approach is not doing any good in cross browsers reporting.
on the other hand, past week microsoft released ssrs 2016 with pure html5 viewer that eliminated the need for activex installation [which was the only downside for using ssrs on non-ie browser]
ssrs 2016 viewer fit perfectly in asp.net core eco system perfectly
but no official statement regarding asp.net core support was declared.

is it all blocked by System.Drawing?? because even itextsharp hadn't release a library until now.
if it is System.Drawing then at least windows implementation can be completed before [linux and OSX] in order to increase adoption for current windows developer instead of waiting for the full cross-platform implementation for System.Drawing

I hope this post will make the team reconsider some priorities to enable ssrs within asp.net core

with respect for MvcReportViewer mentioned in previous post (it is a wrapper around webforms viewer) and it helped alot of mvc developers in the past to overcome the lack of mvc report viewer in mvc1 to mvc5 [Thanks so much ilich], I hope to see a full solution because ssrs was not a first class priority and people kept quite about it in pre-core mvc.

@mmgafri
Copy link

mmgafri commented Jun 8, 2016

Please developers,
forward this issue to your colleagues in order to comment about it.
this might give a priority for it and motivate the team to do something.

@MaximRouiller
Copy link

@ddddddddeee22211 It's a V1.

You don't ship with SSRS support initially. The support with SSRS would probably come from the SSRS team and not the .NET team. Since we're not even out of RC yet, I don't see this as a critical feature in V1.

If you need to do reports, may I recommend just running the webforms version? Yeah. It's old. But at least it works and it's supported.

If you need X-Plat reports, I'll recommend something like Chartist. It allows you to generate charts directly on the client. Add a CSS file for printing purposes and boom. You have reports that can be printed.

@mmgafri
Copy link

mmgafri commented Jun 9, 2016

from your perspective it might not be critical
but some other developers are considering it very important for their projects because once they develope an app and go live with it, development tasks get holded and reporting tasks become daily routine tasks. also some projects handle reports creation to BI (business intelligence) team who knows how to use ssrs but dont have an idea about asp.net core.

the aim of my post was to understand ssrs position within asp.net core eco system. or if it will be ignored as in mvc1 to mvc5. ssrs team are within microsoft and asp.net core team may discuss the issue with them.
what drove me crazy was when i saw ssrs 2016 release note past week without mentioning anything about asp.net core. while on the other hand you see continous support for azure within asp.net core.believe me if we didn't rise a demand for ssrs, it will be ignored as in the previous mvc 5.

your advice about using webforms is an example about slowing down adoption of core initiative.at least if I had a statement about wether it will be supported or not , I'll be able to make strategic decisions about it.

thanks for chatist tip. I'll check it out and I hope you understood my point of view.

@MaximRouiller
Copy link

@ddddddddeee22211 Ahhh... then I can't answer.

Right now, the only way to make SSRS components work on ASP.NET is on WebForms.

If you want their strategic position or if they will support it, we'll need to wait for an MS Employee to answer.

Maybe we can /cc @coolcsh ? He might not answer here but a blog post clarifying the position would be nice.

@jtarquino
Copy link

In the SSRS team we are aware of the limitations of the ASP.NET WebForms and we are actively investigating and working in new options for the Report Viewer control
Thanks

@MaximRouiller
Copy link

@jtarquino

Thanks for the reply man!

We've been wanting an alternative since MVC. 😜

@mmgafri
Copy link

mmgafri commented Jun 19, 2016

That just made my day. [happy ending]
Thanks @jtarquino , @MaximRouiller for all effort.

@boemark
Copy link

boemark commented Jun 30, 2016

@jtarquino
That sounds great :-)

Can you say anything about when you expext to release first version of the "new option" for Report Viewer Control ?
(Are there any roadmap/plan for this?)

Br.
Boe

@jtarquino
Copy link

Unfortunately I don't have a timeline to share at the moment

@bethwellagat
Copy link

have you tried using a Library by installing a Package on Package Manager Console and type following command into command window.

PM> Install-Package ReportViewerForMvc
although i have tried on web-forms and they look pretty good.

untitled

@KerolosMalak
Copy link
Author

KerolosMalak commented Aug 1, 2016

@bethwellagat
again fire error "the dependency ReportViewerForMvc doesn't support framework .NetCoreapp"
notes:
working on ASP.NET Core project

@Eilon
Copy link
Member

Eilon commented Sep 29, 2016

@jtarquino ping on this. Looks like there's more interest: aspnet/Mvc#5332

@Eilon
Copy link
Member

Eilon commented Sep 29, 2016

@jtarquino BTW if you want to start some discussions with my team, please email me and we can chat.

@MaximRouiller
Copy link

Ohhh me like! The ball is rolling! 😀

@alanjuden
Copy link

Hey everyone, I just finished writing a custom port of the report viewer control using the ReportExecutionService.asmx that's built into SSRS and I was targeting ASP.NET MVC. I had someone suggest porting it to .NetCore & MVC so I have completed that. Give it a try and let me know what you guys think: https://github.com/alanjuden/MvcReportViewer

Alan

@wqwalter
Copy link

It looks like it has been about three months since ReportViewer in ASP Netcore MVC has been discussed here. I am working with the version Alan Juden has provided in a project I am moving from WinForms to netcore. Is there any signs Microsoft is stepping up to provide first class SSRS ReportViewer support or have they put SSRS in the same closet they put Visual FoxPro into a few years back?

@Prost98
Copy link

Prost98 commented Mar 27, 2017

Any progress MS? Best option for now is to use a third party tool like Telerik Reports for browser rendering and SSRS backend for report subscriptions. Maybe as ddddddddeee22211 wrote, SSRS 2016 already has capability via HTML5 rendering engine but no documentation exists?

@MaximRouiller
Copy link

Hey @Eilon.

Any news since September? Especially since you guys now launched 1.0 (congrats!), pressure must be down a bit.

Anything you can share?

/cc @jtarquino

@jtarquino
Copy link

Nothing that I can share yet, as soon I have news for .NET core you will be the first one to know.
As you mentioned we just released the latest nuget for the ASP.NET Webforms and Winforms control

@bcsmith100
Copy link

bcsmith100 commented Apr 7, 2017

I would like to add my prompt to the team as well... This is a major issue. I appreciate AlanJuden's solution, but we need an "official" solution... Given that core 1 has been out for months now it would be helpful to have some word on the status of this. If you could get us word on the timeline for a solution that would be something. This issue is large enough that it will prevent us from using mvc core. One note. We really need a solution that gets around the need for the users to log into the ssrs server. This is why my project has to use the current reportviewer (using reportviewer we have the mvc project provide a standard login to the ssrs server for all users)

@mmgafri
Copy link

mmgafri commented Apr 22, 2017

Sql server 2017 is community preview2 now
And
.net standard 2.0 release is close with the latest announcement
And still no word on native asp.net core reporting service viewer
Please invite other developers to this issue to give feedback and make the team aware of the need for such an effort for a masterpiece framework that every developer is dreaming about.

@figuerres
Copy link

@jtarquino : is there a forum or uservoice for SSRS ?
how can users contact the SSRS team ?

@jtarquino
Copy link

@figuerres
Copy link

figuerres commented May 1, 2017 via email

@timClyburn
Copy link

Hi,

We are looking to migrate some of our websites etc to asp.net core but some include an SSRS Report Viewer Control. Is there any progress on a report viewer control for .net core?

Thanks
Tim

@ikourfaln
Copy link

ikourfaln commented May 8, 2017

if you are targeting Full .NET 4.x and not .NET Core, please take this #2022 in consideration before moving to ASP.NET Core.
ASP.NET Core 2 will not support Full .NET 4.x

@ststeiger
Copy link

ststeiger commented Sep 17, 2019

@PentaTech, @g-rad: added.

@brad0000
Copy link

brad0000 commented Oct 2, 2019

@ststeiger good effort on this, could you please add gitlab account brad0000?

@ststeiger
Copy link

@brad0000: Done.

@wyepez
Copy link

wyepez commented Oct 2, 2019

Hi @ststeiger , could you add me as well? gitlab account: wyepez. thanks

@ststeiger
Copy link

@wyepez: Added.

@choudeshell
Copy link

@ststeiger Can you please add me as well?

Gitlab username: choudeshell

@ststeiger
Copy link

@choudeshell: Added.

@Muaddib787
Copy link

Can you please add me? Thanks!

@Muaddib787
Copy link

Does your solution work with .rdlc (as well as server side .rld)? Thanks

@ststeiger
Copy link

ststeiger commented Oct 7, 2019

Does your solution work with .rdlc (as well as server side .rld)? Thanks

@mpirritano: Yes, in fact, there's not much difference between RDL and RDLC.
But it's web only. No Windows-Forms.
I need a gitlab account to add you, not github.

@Muaddib787
Copy link

@ststeiger Thanks - I've created a GitLab account now :@mdpirrit

That's great - I only need it for ASP .NET Core targeting .NET Core. Thanks!

@ststeiger
Copy link

@mpirritano: Added, you should have gotten an email to the email account you used to register gitlab.

@Muaddib787
Copy link

Got it; thanks!

@Muaddib787
Copy link

@ststeiger it works great except it can't render Charts. - it renders the chart area with the error :"Could not load file or assembly "System.Windows.Forms, Version=4.0.0.0"

Is this a known limitation or am I missing something?

Thanks

@Muaddib787
Copy link

@ststeiger Also, it doesn't appear as if subreports are supported. i.e. there doesn't appear to be a subreport processing eventhandler to add data sources to the subreport instance

Thanks

@azikaa
Copy link

azikaa commented Oct 9, 2019

Can you please add me? Thanks! @ashabyralieva

@azikaa
Copy link

azikaa commented Oct 9, 2019

Работает ли ваше решение с .rdlc (а также со стороны сервера .rld)? Спасибо

@mpirritano : Да, на самом деле, между RDL и RDLC нет большой разницы.
Но это только сеть. Нет Windows-форм.
Мне нужна учетная запись Git Lab, чтобы добавить вас, а не GitHub.

Можете ли вы добавить меня? Спасибо! @ashabyralieva

@ststeiger
Copy link

ststeiger commented Oct 10, 2019

@azikaa: Done. Добавлено;)

@mpirritano:

Is this a known limitation or am I missing something?

Yea, one limitation I was aware of that it could exist.
And also, it has a problem with image output in HTML.
Open points.
I didn't even think of subreports just yet.
Sadly, we have a few of them, too, so this will be my problem as well.
Speaking of it, I don't even know how subreports are handled in the normal ReportViewer on the full framework, specially as they can be recursive.

Probably it has a problem somewhere, because "System.Windows.Forms, Version=4.0.0.0" doesn't exist in that version in .NET Core, and also, the assembly is called System.NetStandard.Forms instead in the ReportViewer for .NET Core. Might work on full framework, because there System.Windows.Forms, Version=4.0.0.0 does exists.

The problem with System.Windows.Forms can probably be rectified as easily as putting the assembly-name and version (wherever it hides in the sourcecode) into an ifdef, the subreports rather not I guess.

I still have to finish a report-sending service this week, so I might be able to look at the System.Windows.Forms issue some time next week.

As far as subreports go: they are a bad idea anyway, tend to create problems with PDF and Excel, and in case you have just 1 report, I'd recommend to see if it isn't somehow possible to eliminate the subreport altogether somehow, and make everything contained in one report.

@azikaa
Copy link

azikaa commented Oct 10, 2019

Добавлено
How to get database COR_Basic_SwissLife_UAT?

@ststeiger
Copy link

🤣 Haha, good one, you don't, that DB is confidential.
But you can make your own example report, using your own database.
You should see from the example how to use it.

@Muaddib787
Copy link

@ststeiger Thanks. Actually, I see that there is SubreportProcessing event defined in AsNetCore.Reporting.InternalLocalReport. I may try creating a public interface for this and see if I can pass data sources to subreport intances. I may not get to this until next week as well...

I try to avoid Subreports as well, but I've found them necessary in cases were you need a repeating section within a repeating section. With regards to Excel, it's possible to render each subreport instance as a worksheet in excel with rdlc/rdl

@k290
Copy link

k290 commented Oct 10, 2019

Reposting this for newcomers.

Everyone in this thread should vote for this to be added, here: https://feedback.azure.com/forums/908035-sql-server/suggestions/33241936-develop-a-ssrs-reportviewer-for-asp-net-core

In March of this year it was 7th from the top.

Now, we've got it up to 2nd from the top of the SQL Server suggestions: https://feedback.azure.com/forums/908035-sql-server?category_id=325159

Can we beat Dark Mode?

@Muaddib787
Copy link

Muaddib787 commented Oct 10, 2019

@ststeiger I actually had a little time today and was able to successfully render reports with subreports in .docx, .xlsx, and .pdf.

As a quick test on my local copy - I changed the access modifier of the "localReport" property of the "LocalReport" class from "internal" to "public". Then I could write a handler for the "SubreportProcessing" event as I always would (where I would read the value of the parameter to the subreport instance and use it to filter a dataset that I would pass into the datasource of the subreport instance)

I have no idea how to fix the chart rendering issue with .NET Core; so if you ever able to reach a solution that would be amazing. But other than that, I think your solution does everything I need it to do (I personally never render reports in HTML format)

Thanks

@azikaa
Copy link

azikaa commented Oct 11, 2019

export- word, excel not woking ?
FormatException: The header contains invalid values at index 0: ''

the service is very slow. what can be done? Please help....

@azikaa
Copy link

azikaa commented Oct 11, 2019

Hey everyone, I just finished writing a custom port of the report viewer control using the ReportExecutionService.asmx that's built into SSRS and I was targeting ASP.NET MVC. I had someone suggest porting it to .NetCore & MVC so I have completed that. Give it a try and let me know what you guys think: https://github.com/alanjuden/MvcReportViewer

Alan

export- word, excel not woking ?
FormatException: The header contains invalid values at index 0: ''

the service is very slow. what can be done? Please help....

@ststeiger
Copy link

@azikaa: Are you using MvcReportViewer, or AspNetCore.ReportViewer ?

@mkArtakMSFT mkArtakMSFT added the External This is an issue in a component not contained in this repository. It is open for tracking purposes. label Oct 14, 2019
@mkArtakMSFT
Copy link
Member

We're closing this issue as it's not directly relevant to this repo and based on the comments here the SSRS team is already aware of this feedback. Given the amount of comments this has got it's now unmanageable.

@k290 's response is the most actionable one here, so please follow his suggestion here:

Reposting this for newcomers.

Everyone in this thread should vote for this to be added, here: https://feedback.azure.com/forums/908035-sql-server/suggestions/33241936-develop-a-ssrs-reportviewer-for-asp-net-core

In March of this year it was 7th from the top.

Now, we've got it up to 2nd from the top of the SQL Server suggestions: https://feedback.azure.com/forums/908035-sql-server?category_id=325159

Can we beat Dark Mode?

@dotnet dotnet locked as off-topic and limited conversation to collaborators Oct 14, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
External This is an issue in a component not contained in this repository. It is open for tracking purposes.
Projects
None yet
Development

No branches or pull requests