Script combining made easy [Overview of the AJAX Control Toolkit’s ToolkitScriptManager]

This blog has moved to a new location and comments have been disabled.

All old posts, new posts, and comments can be found on The blog of

See you there!

Comments (22)
  1. fmarguerie says:

    The technique used to combine scripts makes it really difficult to use with URL rewriting for example.

    Would it be possible to still create a HTTP handler and offer it as an option? It would solve several problems like the additional query to each page and enable URL rewriting.

    I posted this as a work item in CodePlex yesterday:

  2. David Anson says:


    Thanks for the feedback! We’ll look into what might be involved with supporting an HTTP handler in addition to the current technique as part of the work item you opened. As I note in the blog post, that would require folks to have a certain level of control over the web server (i.e., it may not work for all hosted scenarios), but when it’s possible to configure a handler, it could be a nice improvement to ToolkitScriptManager. Great suggestion!

  3. LA.NET [EN] says:

    Besides fixing some bugs and adding some new features to the existing controls, the new release of the

  4. Hmm – do we really need a separate handler or would an ASHX do?

  5. Delay's Blog says:

    A short while ago we made available the 10618 release of the AJAX Control Toolkit . This release addresses

  6. Delay's Blog says:

    The 10606 release of the AJAX Control Toolkit introduced ToolkitScriptManager, a new class that extends

  7. David Anson says:

    Per the above trackback, the 10618 release of the AJAX Control Toolkit has a number of improvements to ToolkitScriptManager – including support for the URL rewriting scenario Fabrice mentions above via the optional CombineScriptsHandlerUrl property:

  8. Depuis quelques temps déjà, les dernières versions des Ajax Control Toolkit intègre un nouveau contrôle

  9. dmose says:

    Awesome tool… however, can we use it to combine regular javascript includes? Or even CSS files?

  10. David Anson says:


    Thanks! As it’s currently implemented, ToolkitScriptManager is pretty closely tied with the way ASP.NET AJAX’s ScriptManager processes and sends down JavaScript files, so I don’t think it’s directly applicable to other JS/CSS files. However, the basic concept is just as relevant and could probably be implemented similarly for use with general-purpose files. We just haven’t done so here. 🙂

  11. trent.niemeyer says:

    Has anybody noticed the increased PreRenderComplete times when using this control?  My best guess is that there is some expensive operation using this method when trying to combine scripts.  The implications were significant within our app.  Script combination only saved a *fraction* of total download size, where I gained .7 seconds on the server for rendering this script.  Definetly a deal breaker.

  12. This is probably already well known and well documented, but I still occasionally see people bemoaning

  13. How is this affected by the newly release CompositeScript functionality of scriptmanager in 3.5SP1?

    Can we use the new functionality instead somehow?


  14. David Anson says:,

    While ToolkitScriptManager should continue to work as it has, you should also be able to switch to the new script combining functionality in ASP.NET 3.5 SP1 as your schedule permits.

  15. moizdhanji says:

    try following link … it works very well

    Moiz Dhanji

  16. shanoyan says:

    When I run a page that has a CalendarExtender (the same is true for most of the controls, no patience to go through all of them) on it I get an error: “Sys.Extended.UI” – is null or not an object.

    Is there a work around besides setting the CombineScripts="false", which kind of voids the great idea of script combining?

    I’m using the AjaxControlToolkit.Binary.NET35.

  17. David Anson says:


    I'm afraid I don't have any experience with the release you're using… My ideas would be to see if ASP.NET's built-in script combining (added after we created ToolkitScriptManager) will work for your scenario – or if there might be a version mis-match that's causing Sys.Extended.UI to be referenced when it shouldn't be.

  18. Michael Freidgeim says:

    With ScriptManager in .Net 4 with CompositeScript functionality, is any reason to use  ToolkitScriptManager ?

    If not, it would be good to put an UPDATE at the top of the article, stating that the ToolkitScriptManager is out-dated.

  19. David Anson says:

    Michael Freidgeim,

    Thanks for pointing that out – I've added a note as you sugest! 🙂

  20. Azim says:

    So, ToolkitScriptManager is out-dated? is there any point in replacing <asp:scriptmanager> with ToolkitScriptManager for the date textbox?

  21. Azim says:

    so the  ToolkitScriptManager is out-dated now? is there any point in updating the <asp:scriptmanager with  ToolkitScriptManager now?

  22. David Anson says:


    I'd probably start by using ScriptManager and if you find it does everything you need, then there's not much reason to switch. 🙂

Comments are closed.

Skip to main content