Hi everyone,

I work for a module development company, we used Telerik controls extensively in our modules because in the past that was a good option (we have a Telerik license). Now, we are thinking on how to migrate our modules (100.000 lines of code), and this is important to explain why we are just planning now, it will be a really big project to do this.

 One question about this migration, is what we will use in the UI (now that will be MVC). And the questions is, does DNN have something in mind? what control set if any will you use? this is something that you are deciding?

 I realize that is probably too early to know how the UI will look, but maybe you already have some decision, or at least possibilities, and we need to plan very carefully, and as soon as possible.

 Thanks

Javier

Javier,

  The recommendation for DNN neXt development will be to focus on using JavaScript based UI elements.  This approach will work whether you are using MVC or going straight to a SPA style of development.  The other nice benefit is that you can actually begin that work now as JavaScript UI elements will work with any version of DNN.  The DNN platform has used both JQuery UI as well as some js controls we have developed in house.

 Also, note that in DNN 8 we are de-coupling Telerik from the core platform.  While Telerik will not be used in the platform, it will still ship with the platform and will be easily installable in those cases where Telerik is required by modules like yours.  This should not be a breaking change.

If you already have a Telerik license and want to continue using their technology, why don't you make the changes to your code and use Telerik independently of DNN and deploy your licensed Telerik assembly with your module? Although I am not sure how this works if you want to deploy your version if DNN comes with its own Telerik assembly. Two versions can't coexist in the bin folder. I am not sure when or if DNN will stop including Telerik in DNN. I know it's being deprecated but I don't know if this means it will go away completely. It exists in DNN 8.  Will it be included in DNN vNext? I don't know myself.

Maybe your customer's DNN will need to remove DNN's Telerik assembly and have yours only, and have the proper assembly redirections in web.config. I am assuming the newer version of Telerik is backward compatible with DNN's Telerik version. This will require testing. I think DNN's Telerik version is a few versions behind Telerik current version. It's probably even custom built to be used in DNN only. I don't have more details. Your Telerik version will have more features and bug fixes.

Another option is to deploy the same old Telerik version that DNN uses.