Identifying Telerik ASP.NET for AJAX version from DLL's

[Robert Columbia]

So it seems that I've come into a poorly documented set of ASP.NET solutions that collectively include references to several Telerik DLL's.  I have been tasked with evaluating how easy it would be to upgrade to the latest version of Telerik's ASP.NET for AJAX controls, but I currently am unsure where we are in terms of versions.

I found the following:

radeditor.net2.dll version 7.2.0.0
telerik.web.ui.dll version 2008.2.826.20
telerik.web.ui.dll version 2009.2.826.35
telerik.web.design.dll version 2009.2.826.35

So, basically, I'm evaluating whether or not we can take everything that references one or more of these dll's and upgrade them to the latest Telerik for ASP.NET AJAX.  Obviously this will have to be tested, but I need to give a report indicating what likely hurdles we are going to face.  If possible, I'd like to get all of the solutions using a single version, the latest.

[Dobromir]

Hi Robert,

According to the listed DLLs and versions that are referenced in your project, it seems that you are using RadEditor Classic and RadControls for ASP.NET AJAX - the AJAX suite is combined in a single DLL. However, I am not quite sure how you have referenced two different versions of Telerik.Web.UI.dll.

Regarding upgrading RadControls for ASP.NET version you can find e detailed tutorial in the following KB article:
Updating RadControls for ASP.NET AJAX to another version or license

In general the latest version should be fully compatible with the 2009.2.826.35 one, except for few breaking changes which may or may not affect your application.

If you are planning to swap the classic editor that is used currently with its AJAX version you can follow the guidance from this help article:
Migration from RadEditor Classic to RadEditor for ASP.NET AJAX

Regards,
Dobromir
the Telerik team

[Allen]

I have a possibly related question.  My client has alerted me of the following which means nothing to me but probably does to you:

The identified system was running a version of the Progress Telerik UI that was affected by a JavaScriptSerializer Deserialization issue. Upgrade to the latest vendor supported version of Progress Telerik UI.

Can you tell me the first version of Telerik.Web.UI (Ajax) that does NOT suffer from this, by version # and specific release date, and tell me if I can just pop in the right DLL nearest the deployment date of the client's app and resolve the problem.

I have 0 budget to rebuild that old code.

This is fairly urgent.

 

Thank you.

[Vessy]

Hi Allen,

In order to protect against the JavaScriptSerializer Deserialization vulnerability, we recommend that you upgrade to the latest version of our controls (that you are licensed to) or at least to version R1 2020.

We have uploaded a complimentary R1 2020 license for all of our licensed clients, so you can also download it from the Download section of your licensed Telerik account. Look for version 2020.1.114 (or later) in the Version dropdown and download the Telerik_UI_for_ASP.NET_AJAX_2020_1_114_Dev_hotfix.zip archive:
https://www.telerik.com/account/product-download?product=RCAJAX

You can see how to update your project here:
https://docs.telerik.com/devtools/aspnet-ajax/installation/upgrading-instructions/upgrading-a-trial-to-a-developer-license-or-to-a-newer-version#manual-upgrade

Regards,

Vessy
Progress Telerik

[Allen]

My problem is that the deployed app needs to be updated without being rebuilt.  Is it possible I can just pop in the DLLs and it will work?

[Allen]

So version 2019.3 is no good?

[Allen]

I will try the 2020 R1.  I will ignore 2019.3 ...

[Vessy]

Hi Allen,

Yes, in order to make your apps fully secured you will need to upgrade at least to version 2020 R1. If the application is of type "Web site", you can only replace the DLLs without rebuilding. Otherwise, the apps have to be rebuilt with the newly referenced DLLs.

Regards,
Vessy
Progress Telerik

[Allen]

Not to seem stupid, but what's the difference in a Web Site and a Web  Application?  Up until now I have been able to tweak the thing by just dropping a new release application dll in the bin directory and restarting. 

Does that mean I am building a web application?

Sad face....

[Vessy]

Hi Allen,

One of the main differences between a Web site and a Web application is that the former refers all DLLs from its bin folder automatically, while the later needs a manual reference to the new DLL and rebuilding after each change. You can find very detailed information about the differences between the both project types here:
https://docs.microsoft.com/en-us/previous-versions/aspnet/dd547590(v=vs.110)

There is also a pretty useful post on this top in the following SO thread:

https://stackoverflow.com/a/398049

Regards,
Vessy
Progress Telerik