try to load the Default.js in the <Scripts> section of the ScriptManager and let me know if it works.
Hi Garbin:
One word- fantastic!! Thanks a ton!! So, when coding a page for ATLAS, should one always use the script include in the ScriptManager (for uniformity, at least), or only if it utilizes web services? I've been refactoring an existing application (originally asp.net 1.1) to ASP.NET 2.0 features and ATLAS, and before this problem, I've been using the regular Javascript includes. Should I change the other pages to include the scripts through Scriptmanager? Thanks.
Hi,
if the page is Atlas-enabled, I would surely include all the external .js that contain Atlas stuff into the <Scripts> section.
But why, though? Anyone have any idea? It seems perfectly reasonable to have javascript includes on your Atlas page...
The best reason is for consistent script loading order, otherwise you potentially have timing issues and referencing issues, i.e. if you have some script which depends on another script include in your page, if you load all your scripts using script manager, you have confidence that all those scripts will be loaded in order, while if you don't use script manager for all your scripts, the loading order of your scripts is likely to be less predictable.
Hope that helps,
-Hao
No comments:
Post a Comment