9

The newest Report Viewer for Visual Studio 2017 has some bugs that prevent us from using it. We’ve downgraded to Microsoft ReportViewer Runtime 2015 for Web Forms (v 12.0.2402.15). However, the report designer in Visual Studio creates new reports in the new “2016” format, and even editing old reports upgrades them to the new format as well. The older Report Viewer doesn’t understand the new format and bombs.

The new report designer is an extension to Visual Studio, “Microsoft Rdlc Report Designer for Visual Studio,” version 14.2. We haven’t found an earlier version of the designer available as an extension.

We’ve tried installing an earlier version of SQL Set Data Tools, but the report designer was still the same. We also haven’t found a separate download for the earlier report designer.

Is there a way to add the older report designer to VS 2017? Or do we have to downgrade to VS 2015?

(A similar problem here: Change RDL version for RDLC Reports in Visual Studio 2017)

Sandy Gettings
  • 693
  • 5
  • 21
  • Would you be able to provide more details of your implementation? Why do you need to downgrade to an older version? Are you using webforms, MVC but trying to embed inside an IFrame? Which version of SQL are you using? – Charles Jul 31 '18 at 19:41
  • Hi, Charles. We needed to downgrade because of a number of problems, some of which were fixed in a follow-up version of the ReportViewer. We also wrote some JavaScript code to fix other issues when displaying reports within a jQuery UI tab control. Our usage is on an aspx web form, no iframes, SQL Server 2014. – Sandy Gettings Aug 01 '18 at 20:16

3 Answers3

0

The problems in ReportViewer that made it unusable for use were partially resolved in a later version. For example, the CSS in the ReportViewer changed the styles in the rest of the surrounding web page, which was pretty horrible (now fixed). We also saw problems of the viewer's export button drop-down list positioned far from its intended location. We had to fix that with custom JavaScript on the page.

Sandy Gettings
  • 693
  • 5
  • 21
  • 1
    This is not an answer, and shouldn't be posted as one. If you want to add additional information to your question, use the edit link (below the tags) to do so. This space is for a single use, which is indicated by the **Your Answer** heading above the space where you typed it. – Ken White Dec 12 '18 at 00:59
0

You can include/add any RDLC created on VS 2015 to VS 2017 by click on add existing item and select the RDLC directly from your local location and will run on your VS .Add existing item

ayman sayed aly
  • 21
  • 3
-2

From what I can tell, ReportViewer for Visual Studio 2017 which is Version 14, is for compiling in Framework 4.5. My application is depended on 4.0 and if I switch then a bunch of other libraries need to be updated as well. I would rather get the previous version of ReportViewer 12 working, as it was working for my application without issues.

With ReportViewer Designer 14 for VS2017 installed, there is an error in the design of the page, and the application deployed and running on the server does not render the Report.

So, which way to move? Up or back...and how.

IrvineCAGuy
  • 211
  • 2
  • 12
  • This looks like a question more than an answer. If you have a question, either comment somewhere relevant or post a new question! – kebbaben May 29 '20 at 07:37