Assistance Required for Telerik.Web.UI Version Upgrade Issue

[Arvind]

Dear Progress Team,

 

We are currently facing an issue with upgrading Telerik.Web.UI.dll  version from 2021.3.1111.40 to the 2024.4.1114.462 in our application.

Our application uses the RadScheduler component, which was functioning without any issues prior to the upgrade.

However, after upgrading to the 2024 version of Telerik.Web.UI, the Scheduler component begins throwing the attached error (stack trace attached Error2.png).

Upon investigation, it appears that the 2024 version of Telerik.Web.UI has a dependency on Newtonsoft.Json version 13.0.

Currently, our application utilizes Newtonsoft.Json version 12.0.

Upgrading to version 13.0 is not feasible in the short term due to multiple dependencies that require comprehensive testing.

 

We kindly seek your clarification and assistance with the following questions:

 

1. Can you confirm whether the Telerik.Web.UI 2024.4.1114.462 version has a dependency on Newtonsoft.Json version 13.0?
2. Is there any workaround available to resolve this issue without upgrading to Newtonsoft.Json version 13.0?

 

Your assistance and guidance on this matter would be greatly appreciated.

 

Thank you, and we look forward to your response.

 

Best regards,
Arvind Pandey.

 

[Rumen]

Hi Arvind,

I can confirm that the Spreadsheet control part of Telerik.Web.UI version 2024.4.1114.462 has a dependency on Newtonsoft.Json version 13.0 (you can find more details here). Please be aware that Newtonsoft version 12.0, has critical vulnerabilities and you should consider upgrading to ensure security.

Workaround with Binding Redirect

As a temporary solution, you can apply a binding redirect in your application's configuration file. This will allow you to redirect the Newtonsoft.Json assembly from version 12.0 to version 13.0 without immediately upgrading your existing codebase. Here is how you can implement the binding redirect:

<configuration>
  <runtime>
    <assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
      <dependentAssembly>
        <assemblyIdentity name="Newtonsoft.Json" publicKeyToken="30ad4fe6b2a6aeed" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-12.0.0.0" newVersion="13.0.0.0" />
      </dependentAssembly>
    </assemblyBinding>
  </runtime>
</configuration>

This configuration should help mitigate the immediate issue with the RadScheduler component by aligning the version requirement without a full upgrade of Newtonsoft.Json at this time. However, please ensure to thoroughly test your application to confirm compatibility with this workaround.

If you have any further questions or require additional assistance, feel free to reach out.

Regards,
Rumen
Progress Telerik

[Sathyendranath]

Hi Rumen,

The above mentioned approach (i.e. binding redirect) still necessitates deploying the Newtonsoft.Json 13.0.  

Please confirm.

Thanks

Sathyendranath

[Rumen]

Hi Sathyendranath,

Yes, the binding redirect approach still necessitates deploying Newtonsoft.Json version 13.0, as the Telerik.Web.UI assembly relies on specific features and fixes introduced in that version. The redirect only allows compatibility without modifying your existing code but requires the newer assembly to be present.

 

Regards,
Rumen
Progress Telerik