Hi Jon,

To dinamically load scripts on demand in my applications, I now use the dnn.dom.loadScript method  from dnn.js.
To make life more convenient I found this technique, which allows to load scripts, directly from embedded resources.

Here's one example of how this technique can be applied:
File:  dnn.js , line 1022

dnn.dom.loadScript(dnn.dom.getScriptPath() + 'dnn.scripts.js', null, oRef(aSrc, aText, callBack));

can be changed in:

dnn.dom.loadScript('<%=WebResource("dnn.scripts.js")%>', null, oRef(aSrc, aText, callBack));

Now,  to allow the url substitution, we need to set the required attribute for the dnn.js:

<Assembly: System.Web.UI.WebResource("dnn.js", "text/javascript", PerformSubstitution:=True)> 

Finally, we have to embed the dnn.scripts.js

<Assembly: System.Web.UI.WebResource("dnn.scripts.js", "text/javascript")> 

I hope this helps.

Regards 
Manzoni Fausto

What you say is correct, although I do not know exactly the impact that the use of embedded scripts can have in terms of performance,(there are a number of applications that utilize embedded scripts).

However, there is another performance issue that you might consider, that is the number of HTTPRequest required to render the page, as documented here.
In DNN each module can have its own CSS and more than one javascript file,(especially an ajax module).
At the end a page can require a lot of external files to be rendered.
Adding script references through the Script Manager, gives the possibility to combine all script references,(present in Its collection) in a single compressed file, using an HttpHandler.

An example of this technique, the ToolkitScriptManager, can be found in the AjaxControlToolKit.
I use a similar technique for css added through CSS placeholder.
I know that this may not be suitable for all possible scenarios but, in my case, the performance is significantly improved.

"the substutition will not work for the dnn.js file as it is not interpreted by asp.net."
In the ClientApi beta it work.