Telerik Removal

Description of Problem

We still utilize the out of date telerik components in a few places throughout the platform. We need to finish up the complete removal so we can finally remove these components from new installations.

Right now it appears that the digital assets module (dnn file manager) and the Html module are the major items that’s holding us back. They both still reference and make heavy usage on the DotNetNuke.Web.Deprecated web controls.

Solution # 1

Remove usage and replace with asp.net components.

Solution # 2

Rewrite these as a SPA module and fix both the telerik and webforms issue at the same time.

Current Usage

A quick search on the solution found the following areas which should be address. This list isn’t complete and will be updated as additional areas are identified.

• DotNetNuke.Web.Deprecated
• DotNetNuke.Website.Deprecated
• DotNetNuke.Modules.DigitalAssets
• DotNetNuke.Modules.Html

Host Settings

• EnableTelerikCDN
• TelerikCDNBasicUrl
• TelerikCDNSecureUrl

Build Scripts

Module.build (spell checker, assembly copy, package creation) CreateCommunityPackages.build (file copies, package creation)

Other files

Tests\App.config Config\SiteUrls.config WebControlSkin (css styles) admin.css (css styles) dnn.jquery.js (RadComboBox type check)

[bdukes]

I’d be willing to argue that having had the Telerik components in an assembly named DotNetNuke.Web.Deprecated since 8.x is enough of a deprecation warning to remove them in 10.0, but if others want to wait, that’s fine.

[valadas]

I am currently working on a proof of concept for DAM, I would like to have it be a full class citizen of both the Persona Bar and as a regular module but SPA based. I would also like to have feature parity.

It is a bit early to make any promise but I should have something hopefully in a week or two to show…