<%@ Page Language="C#" AutoEventWireup="false" CodeBehind="Default.aspx.cs" Inherits="Default" %> <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head runat="server"> <title>MS CRM SPLA Provisioning</title> <telerik:RadStyleSheetManager id="RadStyleSheetManager1" runat="server" /> </head>Here is what I get.
As I have problems with compression, I need to understand why Telerik has chosen this setting.
Also trying to understand CDN and ASP.NET 4 new features....poor Telerik doc....
When I speak of this in the compression forum, nobody was knowing the effect and reason why ???
Could you expect the Pro/Cons ?
I suppose the team is the same for this forum so.....
Thanks.
CS
3 Answers, 1 is accepted
0
Hi Christian,
I guess by "why Telerik has chosen this setting" you address the VSExtensions scenarios. If this is so, here is a brief explanation of our decision. The scenarios provide a checkbox to enable or disable the site-wide compression level by default. The scenarios suggest the addition of RadScriptManager and RadStyleSheetManager to the page by default, as this is an approach for an optimized output in terms of g-zip compression and combination.
You can find more information about the benefits of using RadStyleSheetManager or RadScriptManager in their respective help articles. Additionally, an explanation of the built-in CDN support is also available for each of these controls.
Kind regards,
Simon
the Telerik team
I guess by "why Telerik has chosen this setting" you address the VSExtensions scenarios. If this is so, here is a brief explanation of our decision. The scenarios provide a checkbox to enable or disable the site-wide compression level by default. The scenarios suggest the addition of RadScriptManager and RadStyleSheetManager to the page by default, as this is an approach for an optimized output in terms of g-zip compression and combination.
You can find more information about the benefits of using RadStyleSheetManager or RadScriptManager in their respective help articles. Additionally, an explanation of the built-in CDN support is also available for each of these controls.
Please let me know if there is anything else specific that you think we are missing in our documentation. We will be glad to improve that and to provide you with the information you need.
Kind regards,
Simon
the Telerik team
Registration for Q1 2011 What’s New Webinar Week is now open. Mark your calendar for the week starting March 21st and book your seat for a walk through all the exciting stuff we ship with the new release!
0
CSurieux
Top achievements
Rank 2
Rank 2
answered on 01 Mar 2011, 03:16 PM
Hi Simon,
Sorry my question was unclear and you missed its object.
The question is why RadStylSheetManager is in the header section ????
Nobody seems to know why and we continue to use it ?????
Have you any explanation ?
Best regards
CS
Sorry my question was unclear and you missed its object.
The question is why RadStylSheetManager is in the header section ????
Nobody seems to know why and we continue to use it ?????
Have you any explanation ?
Best regards
CS
0
Hi Christian,
Sorry for the ommision!
The scenarios offered by VSExtensions for ASP.NET AJAX are meant to provide guidance on best practice.
The RadStyleSheetManager control helps reduce the roundtrips between the browser and the server in terms of css serving, that's why it gets added to the page by default.
The reason it gets added to the <head> tag is that it renders <link> tags. To have an XHTML compliant page the <link> tags need to exist in the <head> tag.
Let me know if that helps.
Kind regards,
Erjan Gavalji
the Telerik team
Sorry for the ommision!
The scenarios offered by VSExtensions for ASP.NET AJAX are meant to provide guidance on best practice.
The RadStyleSheetManager control helps reduce the roundtrips between the browser and the server in terms of css serving, that's why it gets added to the page by default.
The reason it gets added to the <head> tag is that it renders <link> tags. To have an XHTML compliant page the <link> tags need to exist in the <head> tag.
Let me know if that helps.
Kind regards,
Erjan Gavalji
the Telerik team
Registration for Q1 2011 What’s New Webinar Week is now open. Mark your calendar for the week starting March 21st and book your seat for a walk through all the exciting stuff we ship with the new release!