I get the following error using the RadScriptManger with about 15 refrenced scriptRefrences under it as a CompositeScript. I know WHY it's happening (I'm sure its an inherited wall that comes from asp:ScriptManager), I'm just looking for the best way to solve it when using the RadScriptManager:
The resource URL cannot be longer than 1024 characters. If using a CompositeScriptReference, reduce the number of ScriptReferences it contains, or combine them into a single static file and set the Path property to the location of it.
Before I started using the RadScriptManager I had a standard ScriptManager with a set of (3) ScriptManagerProxy's and then split the number of static scripts between them. This solves the issue by keeping 5 or 6 scripts to each given proxy instead of 15 in one. I can't find a RadScriptManagerProxy, only the RadAJAXManagerProxy which I'm assuming needs the RadAjaxManager instead of the RadScriptManager.
Todd Anglins blog post seen [HERE] states:
#######
RadAjaxManagerProxy
If you are familiar with ASP.NET AJAX, then you know that every ASP.NET AJAX page requires a single ScriptManager to function correctly. Most sites that are built with MasterPages simplify this by placing the ScriptManager in the MasterPage so that all ContentPages automatically work with ASP.NET AJAX. To add additional settings to the ScriptManager in a ContentPage, a control called the ScriptManagerProxy is used to declaratively set additional settings. At run time, the ScriptManager looks for instances of the ScriptManagerProxy in child containers and automatically loads any settings it finds.
So it is with the RadAjaxManager and the new RadAjaxManagerProxy. You can now (with no hesitation) add a single RadAjaxManager to your MasterPage and then use RadAjaxManagerProxies in ContentPages and UserControls to configure your Ajax interactions. No more worrying about multiple RadAjaxManagers on the page. No more hand coding to ajaxify all of your UserControls. The RadAjaxManagerProxy gives you the full codeless design-time configurator that's available with the RadAjaxManager, and the RadAjaxManager automatically loads all Proxy settings at run time.
######
1) Whats the real difference between RadScriptManager and the RadAjaxManager? Is the RadAjaxManager a replacement for the RadScriptManager? The term "Ajax" in the name makes me question sticking static composite scripts in there.
2) Should I continue to use the standard "ScriptManagerProxy" to solve this script combining issue? If not, what should I be using with the RadScriptManager, or should I change to the RadAjaxManager?
-Jeremy
The resource URL cannot be longer than 1024 characters. If using a CompositeScriptReference, reduce the number of ScriptReferences it contains, or combine them into a single static file and set the Path property to the location of it.
Before I started using the RadScriptManager I had a standard ScriptManager with a set of (3) ScriptManagerProxy's and then split the number of static scripts between them. This solves the issue by keeping 5 or 6 scripts to each given proxy instead of 15 in one. I can't find a RadScriptManagerProxy, only the RadAJAXManagerProxy which I'm assuming needs the RadAjaxManager instead of the RadScriptManager.
Todd Anglins blog post seen [HERE] states:
#######
RadAjaxManagerProxy
If you are familiar with ASP.NET AJAX, then you know that every ASP.NET AJAX page requires a single ScriptManager to function correctly. Most sites that are built with MasterPages simplify this by placing the ScriptManager in the MasterPage so that all ContentPages automatically work with ASP.NET AJAX. To add additional settings to the ScriptManager in a ContentPage, a control called the ScriptManagerProxy is used to declaratively set additional settings. At run time, the ScriptManager looks for instances of the ScriptManagerProxy in child containers and automatically loads any settings it finds.
So it is with the RadAjaxManager and the new RadAjaxManagerProxy. You can now (with no hesitation) add a single RadAjaxManager to your MasterPage and then use RadAjaxManagerProxies in ContentPages and UserControls to configure your Ajax interactions. No more worrying about multiple RadAjaxManagers on the page. No more hand coding to ajaxify all of your UserControls. The RadAjaxManagerProxy gives you the full codeless design-time configurator that's available with the RadAjaxManager, and the RadAjaxManager automatically loads all Proxy settings at run time.
######
1) Whats the real difference between RadScriptManager and the RadAjaxManager? Is the RadAjaxManager a replacement for the RadScriptManager? The term "Ajax" in the name makes me question sticking static composite scripts in there.
2) Should I continue to use the standard "ScriptManagerProxy" to solve this script combining issue? If not, what should I be using with the RadScriptManager, or should I change to the RadAjaxManager?
-Jeremy