This is a migrated thread and some comments may be shown as answers.

Upgrading Version Creates Bizarre Error

3 Answers 44 Views
General Discussions
This is a migrated thread and some comments may be shown as answers.
Chris
Top achievements
Rank 1
Chris asked on 31 Jan 2018, 08:07 PM

I recently upgraded Ajax UI controls and Reporting to the latest version. Trying to pull up the pages with Telerik controls products an error seemingly unrelated to Telerik - but mismatched versions produced seemingly unrelated errors a few months back on a Telerik upgrade.

I manually went into the web config and changed the version on Reporting - but there is no explicit version for the controls
the only other Telerik dll referenced is the Web ReportViewer - which was not updated, either in development or on the production server
if the problem is a version mismatch how do I find out what it is?

 

 

3 Answers, 1 is accepted

Sort by
0
Rumen
Telerik team
answered on 02 Feb 2018, 01:43 PM
Hi Chris,

I learned from your ticket on the subject that you have solved the problem. Can you please share how with the community?

Just want to add that the only known and documented change in the R1 2018 release is that t
he Telerik.Web.Design.dll assembly is no longer added to the GAC by the automated installer and this can cause design-time errors if you upgrade via the Upgrade Wizard and your project did not have an explicit reference to the Telerik.Web.Design.dll file in the project folder. You can read more in this section of the documentation: Error Creating Control Failed To Create Designer after upgrade to R1 2018.


Kind regards,
Rumen
Progress Telerik
Try our brand new, jQuery-free Angular components built from ground-up which deliver the business app essential building blocks - a grid component, data visualization (charts) and form elements.
0
Chris
Top achievements
Rank 1
answered on 26 Feb 2018, 03:58 PM

the earlier updates replaced the GAC - 2018 version of Ajax UI does not

I added Assembly Binding entries to the web config:

      <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Telerik.Web.UI" publicKeyToken="bla bla bla" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-2017.3.913.40" newVersion="2018.1.117.40" />
      </dependentAssembly>
      <dependentAssembly>
        <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="bla bla bla" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-7.0.0.0" newVersion="7.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>

just above the </configuration> tag

obviously not bla bla bla - but I am not posting my key data....

0
Rumen
Telerik team
answered on 27 Feb 2018, 08:44 AM
Hi Chris,

Thank you very much for sharing your binding redirect solution! 

Actually the public token for Telerik.Web.UI.dll is identical for each release for backwards compatibility. The information is available in the documentation.

Best regards,
Rumen
Progress Telerik
Try our brand new, jQuery-free Angular components built from ground-up which deliver the business app essential building blocks - a grid component, data visualization (charts) and form elements.
Tags
General Discussions
Asked by
Chris
Top achievements
Rank 1
Answers by
Rumen
Telerik team
Chris
Top achievements
Rank 1
Share this question
or