When building a ajax module, i have ran into an issue which has caused me great concern about how dotnetnuke is handling the scriptmanager within the core of community edition.

If i want to build a basic module using ajax cascading drop downs. I need to use a scriptmanager to get it to work, obviously. Since dnn already has the RadScriptManager within the core (pigeon holing me into the telerik scriptmanager), I cannot create my ajax cascading drop downs because i am using the current version of the ajax toolkit which needs the ToolkitScriptManager to run the controls. Now i find out that community edition developers cannot code against the telerik dlls to do ajax functions within their modules. Even though i am not going to distribute the telerik dlls, i am not allowed to even hit it unless its a built in dnn rad control.

I honestly think it is rediculous to put something into the community edition in which i cannot call. We talk about open source all the time, but if i need to create a module for my website and want to use ajax, I am handcuffed. There have been no additions to the "dnn rad controls" and this is frustrating. Why even have telerik in the core of community. We have too much junk in there anyway, and now we have something that we cannot even code against unless you go out and buy a 800$ license.