Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Thursday, April 13, 2017 4:39 AM
Current asp.net web sites are using RV V12. This is what is installed on client's sites.
VS017 changes schema on RDLC from 2008 to 2016. Having to edit RDLC files every time I change it.
I have no RV versions beyond 12 installed.
a) Where do I get RV14 or whatever it is that uses 2016 schema?
b) How do I maintain web apps using RV 12 with VS 2017.
Nothing on Help sites..
Ian Fry Fry Systems Pty Ltd Adelaide, Australia
All replies (6)
Friday, April 14, 2017 6:19 AM ✅Answered
Hi Ian Fry,
Welcome to MSDN forum.
>>Where do I get RV14 or whatever it is that uses 2016 schema?
The Report Viewer Control(version 14.0.0.0) is now shipped as a NuGet package. Because of this, you will not see the Report Viewer Control show up in the Visual Studio toolbox by default. If you have the control with a version of 12.x, removing the ReportViewer Control that is listed in the toolbox, then adding control to Visual Studio toolbar with the steps in the following link:
>>How do I maintain web apps using RV 12 with VS 2017.
As far as I know, reportviewer 12 could be used in vs2017, I recommend you use the latest version, with this update, the Report Viewer control:
- Includes resource files for 14 supported languages
- Supports and renders properly on pages that use ASP.NET master pages
- Supports pages accessed over HTTPS
- Provides improved error messages in some common cases when the control might not be configured properly
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.
Best regards,
Joyce
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].
Monday, April 17, 2017 10:04 AM ✅Answered
Hi,
>>From what I have been told Microsoft has abandoned the GAC concept so...
If Microsoft abandon the GAC concept, it will inform us.
>>Are you now saying that NuGet is official Microsoft Policy?
Yes, it is supported by Microsoft.
>>Do I have to now upgrade each VS Web Site individually?
If there is no issue with report viewer 12.0.0.0 in visual studio 2017, you could not update them. If you want to update it, add the control via Nuget and update the assembly references to version 14.0.0.0. This will include updating the project's web.config and all .aspx pages that reference the ReportViewer control, refer the link in previous reply.( yes, upgrade each VS WebSite individually)
>>What do my clients do - if they run the Nuget package it won't help them...
Do you mean that you want to know it will affect your clients after you publish your web site? There is no effect on your clients.
>>Or am I shipping the control with the website now?
When you publish your website, you need to package all packages include nuget packages.
Best regards,
Joyce
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [email protected].
Saturday, April 15, 2017 5:00 AM
Thanks joyce.
That has resolved part of my problem.
From what I have been told Microsoft has abandoned the GAC concept so...
Are you now saying that NuGet is official Microsoft Policy?
Do I have to now upgrade each VS Web Site individually?
What do my clients do - if they run the Nuget package it won't help them...
Or am I shipping the control with the website now?
Ian Fry Fry Systems Pty Ltd Adelaide, Australia
Tuesday, April 25, 2017 10:51 AM
I now have a further issue...
After changing to RV14 I am getting the following in IE11,Edge and Chrome
Browser not supported
Report Viewer requires a standards compliant browser. Users of Internet Explorer 8 and earlier should switch to a modern browser, or if already using a modern browser target standards mode by adding the <meta http-equiv="X-UA-Compatible" content="IE=edge" > header tag to the host page.
I already have
<httpProtocol>
<customHeaders>
<clear />
<add name="X-UA-Compatible" value="IE=Edge" />
</customHeaders>
</httpProtocol>
in web.config and also added the meta tag to my aspx page
No success.
Ian Fry Fry Systems Pty Ltd Adelaide, Australia
Thursday, May 31, 2018 5:09 AM
RDLC Schema changes from 2008 to 2016 schema on Visual Studio Pro 2017
I was running RDLC Report in WPF Application with 2008 schema and it was working fine.
Now when i tried to add Parameters to report its schema changed to 2016. Now my Report.WinForms.dll version 10.0 does not support this, I Believe. As suggested by Joyce i updated my Report.WinForms.dll to version 14.0 but it still does not work.
Moreover, my Report Viewer control is not added after i followed the steps removing and adding the control again. Throws some framework error which is not the problem for me. as i added the control in wpf App through the same 14.0 reference.
Now i would like to know why it still does not work. When i run my report it says that Report.Common.dll version 14.0 could not be loaded which is not the case as I Installed both the latest 14.0 NugetPackages for Win and Web(which contains Common dll also).
Any suggestions.
Thanks
Shailesh Aggarwal
Tuesday, October 16, 2018 3:14 PM
Yes they did abandoned reportviewer 2017
performance is super duper slow!
compare it to reportviewer 2008 5secs vs 30 secs
10 sec vs 2 minutes if you have lots of formula in your matrix