Hi Guys,

I've been working with DNN for the past 3-4 years and although a lot of strides have been made on improving server side performance, very few changes have been made on the client side. For some reason DNN still uses files like dnn.xml.js and dnn.xmlhttp.js which provide functionality already supported by jquery and the ajax .net library. I'm sure if the DNN team was so inclined they'll be able to remove 80% of all the dnn%.js files. So why do we still need all these old JS files, if they are completely redundant? Furthermore, why is the AJAX.Net library and jquery included when only jquery is needed. Microsoft has thrown all their support behind jquery, so why does DNN auto include the scriptmanager? Why not make the AJAX.Net library an optional feature again for all the developers who still use it, and modify all DNN features to use JQuery instead?

Hi Sebastian,

Appreciate the reply. I'm well aware that DNN has a lot of third party modules relying on it. And a lot of these modules will also break once the methods marked deprecated have been removed from the DNN source.

I don't really see the difference between refactoring the JS, and refactoring the vb code. There will be some losers initially, who don't want to modify their modules. But at the end all the developers/users will be winners, having a faster DNN experience without the JS bloat.

We are currently looking at ways to cleanup our client side code.  Part of the problem is that the person who was doing most of that work has been distracted by work and hasn't been as active lately.  We will be focusing on a consolidation of the client side in the near future.

---

Joe Brinkman
DNN Corp.