LoadScriptsBeforeUI Property

Syntax

[CategoryAttribute("Behavior")]
[DefaultValueAttribute(true)]
public bool LoadScriptsBeforeUI { get; set; }

<CategoryAttribute("Behavior")> _
<DefaultValueAttribute(True)> _
Public Property LoadScriptsBeforeUI As Boolean

[CategoryAttribute(L"Behavior")]
[DefaultValueAttribute(true)]
public:
bool LoadScriptsBeforeUI {
	bool get ();
	void set (bool value);
}

/** @property */
/** @property */

Value

Return Value

true if scripts are loaded before markup for the UI is loaded; false if scripts are loaded after markup for the UI is loaded. The default is true.

Remarks

The LoadScriptsBeforeUI property determines how scripts in the Scripts collection are loaded relative to the markup that constitutes the page UI.

When the LoadScriptsBeforeUI property is true, a <script> element is rendered before the page's UI markup. In this scenario, if UI elements are defined in scripts, the UI will be fully functional when it loads. However, if the script accesses UI elements in the markup that are not yet instantiated, an error might occur. To make sure that UI elements are loaded before accessing them, provide a handler for the load event of the Sys.Application class.

When the LoadScriptsBeforeUI property is false, a <script> element is rendered after the page's UI markup. In this scenario, the UI loads more quickly, but it might not be fully functional if scripts that define additional UI elements have not finished loading.

Assembly: System.Web.Extensions (Module: System.Web.Extensions)