I'm kind of assuming the infragistics controls use scriptresource files similar to the AJAX control toolkit controls. If thats the case is there a way to combine the calls to those script files on call backs? I know Microsoft made some changes between their regular scriptmanager and the toolkitscriptmanager to combine those calls for better performance. I only ask because using an HTTP watch tool, I'm seeing 4 or 5 scriptresource requests on every call back when I use the new WebDataGrid. I recreated the same page with a regular asp.net gridview and only 1 call is made. Thanks for any advice or info on this matter.
I just downloaded the 2009 v1, added it to my project and removed all the 8.3 references. Everything's working okay, but I still see multiple round trips using the httpwatch tool. Is there a property I need to set that combines all the scriptresource calls into one? Or something else I need to add to my page?
FYI: I am using the control inside an updatepanel. I am also using the toolkitscriptmanager vs the regular scriptmanager which from what I've read is the version Microsoft made the Scriptresource change in.
Hi Alexander
I have been looking information about how to avoid the deploytment of so many javascript file that you do not really need.
I have check that for one single component (For example, WebTextEdit), the browser is showing me that a lot of javascript files have been deploied hence the performance is affected.
For example, Infragistics.Web.UI.WebMaskEditor. I am not using any mask so why do need to have this javascript file in my browser?
Someone.. Any suggection??? Advise???
Thanks Alexander.
Any news on what release this will make it into?
Is this suggested to be used as well:
Infragistics.WebUI.Shared.Util.ClientScript.EnableScriptCombining(bool enable)
Long story short the automatic script combining was pulled out at the last moment before the release. It appeared that there were too many problems related to it and we didn't feel comfortable adding the solution without proper testing and confidence that it'll work in all cases.
The main stumbling block with it is that Microsoft generates combined URL for the Java Script include based on the URLs from all of the Java Script files added for combining. The result is the final URL may exceed 1024 character length very easily and a server side exception is thrown.
In the meantime you can combine all files into one using a method described in this article:
http://community.infragistics.com/aspnet/articles/understanding-script-combining.aspx
Most likely you will run into the same problem if too many files are combined. Microsoft's recommendation for resolving it is to split the files into groups and use ScriptManagerProxy to combine separate groups.