Has anyone else noticed this or am I doing something wrong.
Upon getting a new version of the various Telerik suite of libraries, I often end up running the Report Upgrade wizard. That wizard seems to be doing something wrong in VS 2017. Here is an example of what I am seeing.
I have telerikReportViewer-12.0.18.416.min.js and telerikReportViewer.kendo.12.0.18.416.min.js in my existing project. The project is bound to Team foundation Server source control.. Upon running the wizard, the project processes normally and appears to update correctly. That catch I am seeing is that the wizard appears to remove the old version of the viewers from your project and adds the new version to your project. All of this seems to be done outside source control.
I.E., at the end of the upgrade cycle, source control still thinks the 12.0.18.416 items are in your project and that the upgraded versions are not part of your project. A manual update of both is necessary. I do not see this behavior on other suites such as ASPX or MVC/Kendo products.
1 Answer, 1 is accepted
We tested the issue locally updating a Telerik Reporting project in VS 2017 from 12.0.18.416 to 12.1.18.516. We couldn't reproduce the described behavior.
The references in the Html page with the Html5 Report Viewer were correctly updated and successfully added to the TFS source control.
The old version reference were not deleted from the source control. We will investigate the reason for this behavior and try to improve it.
Regards,
Todor
Progress Telerik