Updating report viewer 2016 problem
So if your team has upgraded to VS 2015 Update 3, with the latest SQL Server Data Tools, then you will start to see 2016 report definitions popping up as they get edited. There is no 'official' client runtime download for the v13 report viewer yet, you will have to extract the necessary dlls from the GAC from the server with SSRS 2016 running on it, or from a development machine with the latest Data Tools installed. NET Web Forms apps and shared valuable feedback with us.Today, we’re pleased to announce an updated build that’s generally available for you to use in your production apps.You can find more instructions, information and the source code of the package on my **Git Hub repo.I used the test harness to run a sample report so I was confident that all was good.Also, sometimes when you change parameter values IE11 stops responding or it takes a long time to load the report.You may also find that the toolbar that displays the report controls and export features, appears on multiple lines when viewed with IE11.
Visit Stack Exchange Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Sign up to join this community You upgraded to Internet Explorer 11, now when you preview a SQL Server Reporting Services (SSRS) report you find the print command is not visible in the report viewer.
Turns out they weren't actually having an issue with the print button or anything (as described in my original link), so it is unclear whether it was really the same issue at all.
A few other user complaints (about whether parameters with long drop-downs can be re-sized) seem to have resolved on their own, perhaps by an update to IE 11? I did end up adding section of the Report file, per the suggestions here and the comments in the original link.
Check out this article for a step-by-step walkthrough.
If your existing project references a previous version of the Report Viewer control, you’ll need to update a few references in your web pages and web.config file; see this article for more info.