No matter which method you choose, as a result your script is loaded in the browser. The difference is the way the script is loaded – combined with other scripts in a single file or as a separate file. For more information, see Add resources to your application.
In the code above, you register the Telerik.Sitefinity.Web.UI assembly with the following tags:
Scripts are not loaded in the same order as you have defined them using the ResourceLinks control.
NOTE: The priority the scripts are loaded in is important, not their order in the ResourceLinks widget.
The order in which the Script Manager loads the scripts is as follows:
All of the resource links widgets are processed and the scripts are set for loading. The embedded scripts are loaded by the SitefinityScriptManager. Scripts that are referenced using a relative path are loaded using the System.Web.UI ClientScriptManager RegisterClientScriptInclude method.
Sitefinity CMS recommends that you load your scripts from the same source: either using embedded resources, or by loading them using the relative path to the resource.
To edit the default ScriptManager settings, perform the following steps:
The Page_PreRender method of your widget uses the ScriptManager class for the current page.
For more information about including JavaSript code using Sitefinity CMS Java Script widget, see Java Script widget.
Back To Top
To submit feedback, please update your cookie settings and allow the usage of Functional cookies.
Your feedback about this content is important
Copyright © 2022 Progress Software Corporation and/or its subsidiaries or affiliates.
All Rights Reserved.
Progress, Telerik, Ipswitch, and certain product names used herein are trademarks or registered trademarks of Progress Software Corporation and/or one of its subsidiaries or affiliates in the U.S. and/or other countries. See Trademarks for appropriate markings.
Powered by Progress Sitefinity