Is it a bad idea to use ReportViewer control in MVC 5.2 (.NET 4.5) application

558 views Asked by At

Since ReportViewer must be used with ASPX and that there is a lot of differences between WebForms and MVC, should I still go for a way to include ReportViewer control in my MVC application (as a partial view), or it is better to search for some other option? If it is not god idea to use ReportViewer in MVC, what other options do I have?

1

There are 1 answers

2
meda On

Unfortunately ReportViewer requires viewState and that's not in MVC.

As you notice you will need to go through some hacks to make it work, if you google more you might find some libraries/github repos that will make that process easy.

Your best bet is to build it from scratch and get away from webform technologies but that's not also that easy, I know telerik built such things but it's not free although really worth it.

You just have to see what is the better option for you. This was an advantage of webform, just drag and drop the control and voila, but in MVC it takes more work.