WebResources and ScriptResources

[René]

Hello,

is there any way how to get rid of all ScriptResource and WebResource requests of Telerik controls? I want to use standard script and style bundling. On every page there is always more then 15 requests only for embedded resources. I think it is better to have 1 request for styles and one for scripts. Well, sometimes more, but I want definitely remove all these requests. So any chance to get source scripts, create my own bundles and disable resource requests?

Thanks

[Kostadin]

Hi Raptor,

If you are not using a CDN you could place a RadScriptManager control which unites all the scripts requested by the browser and also place a RadStyleSheetManager which combines all the styles. Additionally you could disable the styles and the scripts for each control by disabling the EnableEmbeddedScripts, EnableEmbeddedBaseStylesheet and EnableEmbeddedSkins.

Regards,
Kostadin
Telerik

[Sunil]

Hi,

I am having the same issue and tried to add the RadScriptManager control in the content page. It resolves the problem what you have mentioned but since our Master page contains the <asp:ScriptManager > tag already, it is not working with the master page and content page. Only one instance of script should be allowed in a page.

Can you please help in this regard asap?

 

Thanks,

Mahesh

[Marin Bratanov]

Hi Mahesh,

Regarding the number of script manager instances on the page—this is the standard behavior of the MS AJAX framework. You should replace the <asp:ScriptManager> from the master page with a <telerik:RadScriptManager>.

To add some more information on the original case, as well as more options everyone can choose from:

RadScriptManager and RadStyleSheetManager will combine the webresource requests for the Telerik resources into one, so you can get that very easily.

The second option I can suggest is using the CDNs we provide and the combined resources we have. This will let you and your users benefit from the aggressive caching this provides.

• for scripts: http://docs.telerik.com/devtools/aspnet-ajax/controls/scriptmanager/cdn-support/combined-request-for-telerik-controls.
• for base stylesheets: http://docs.telerik.com/devtools/aspnet-ajax/controls/stylesheetmanager/cdn-support/combined-request-for-telerik-controls. Note that this only includes the base stylesheets, the skin-specific stylesheets will be in their own requests.

A third option (that I would not recommend because involves too much work for manual bundling) is to disable the embedded resources of our controls and register them manually:http://docs.telerik.com/devtools/aspnet-ajax/general-information/performance/disabling-embedded-resources. This approach does not offer any benefits to the CDN approach. If your app will be used in an Intranet environment where the users will not have access to the cloud, you can create a custom CDN provider on your local machine: http://docs.telerik.com/devtools/aspnet-ajax/controls/scriptmanager/cdn-support/custom-cdn-provider.

 

 

Regards,

 

Marin Bratanov
Telerik by Progress