AJAX Control Toolkit error: ""sys.extended.ui is null or not an object"
By Peter Bromberg
When using the AJAX Control Toolkit you see a strange error: you recieve a client-script exception message that says "system.extended.ui is null or not an object".
The fix is to ensure that the ToolkitScriptManager on the page has the CombineScripts
attribute set to false as shown:
<ajaxToolkit:ToolkitScriptManager runat="server" ID="ajaxScriptManager" EnablePartialRendering="true" CombineScripts="false" />
The ToolkitScriptManager class derives from ScriptManager
and enables the automatic combining of multiple script files in the corresponding
web page. Any scripts (and localized script resources) coming from assemblies
indicating their willingness to have their scripts combined (with the new assembly-level
ScriptCombine attribute) will automatically be combined into one file for download
by the user's browser. This combining action (and the automatic compression of
the resulting file) can dramatically reduce the number of round-trips made by
the browser to fetch scripts and correspondingly improve the page's responsiveness.
While desireable, this behavior can still clobber some pages, causing
the above-referenced error, which is why the CombineScripts="false"
attribute is provided.
AJAX Control Toolkit error: ""sys.extended.ui is null or not an object" (8666 Views)