hello,
i am experiencing Something Weird (tm). in development, my RadControls look 100% normal and good. but after deploying my ASP.NET 2.0 (VS.2005) web application project to our test environment, it gets whackjack. problems:
http://semi-suave.com:81/temp/radError.gif
...what could be causing this!?? to deploy i copied a cleaned, "Publish"-ed version of my project files, which include the 12MB Telerik assembly (Telerik.Web.UI.dll. "RadControls for ASP.NET AJAX").
thanks!!
matt
i am experiencing Something Weird (tm). in development, my RadControls look 100% normal and good. but after deploying my ASP.NET 2.0 (VS.2005) web application project to our test environment, it gets whackjack. problems:
- RadComboBoxes dont render their drop-down lists.
- RadComboBoxes show "select" text next to each one
- RadGrid not rendering itself when empty
http://semi-suave.com:81/temp/radError.gif
...what could be causing this!?? to deploy i copied a cleaned, "Publish"-ed version of my project files, which include the 12MB Telerik assembly (Telerik.Web.UI.dll. "RadControls for ASP.NET AJAX").
thanks!!
matt
4 Answers, 1 is accepted
0
Accepted
Hi Matt,
Could it be that you use RadStyleSheetManager and the website runs in medium trust on the live server? If this is the case, you might have encountered the bug we found earlier. FYI we are now in the final stage of the RadControls for ASP.NET Ajax SP2 release, which will have the problem fixed.
Looking forward to your reply,
Erjan Gavalji
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
Could it be that you use RadStyleSheetManager and the website runs in medium trust on the live server? If this is the case, you might have encountered the bug we found earlier. FYI we are now in the final stage of the RadControls for ASP.NET Ajax SP2 release, which will have the problem fixed.
Looking forward to your reply,
Erjan Gavalji
the Telerik team
Instantly find answers to your questions at the new Telerik Support Center
0
matt
Top achievements
Rank 1
Rank 1
answered on 19 Jun 2008, 07:05 PM
erjan,
yes i am using the RadStyleSheetManager, in attempt to keep page size down. removing it fixes the problem.
sidenote: i am disappointed w/ the HTML-size of the RadControls. i am using about 14 various RadControls plus a RadGrid on my page, which is pretty basic otherwise.. yet page HTML size is 110k.
i see no discernible difference in page size when using or not using the RadStyleSheetManager & RadScriptManager. should i?
thanks,
matt
yes i am using the RadStyleSheetManager, in attempt to keep page size down. removing it fixes the problem.
sidenote: i am disappointed w/ the HTML-size of the RadControls. i am using about 14 various RadControls plus a RadGrid on my page, which is pretty basic otherwise.. yet page HTML size is 110k.
i see no discernible difference in page size when using or not using the RadStyleSheetManager & RadScriptManager. should i?
thanks,
matt
0
matt
Top achievements
Rank 1
Rank 1
answered on 23 Jun 2008, 08:12 PM
Erjan,
can you comment on my last post? i see no difference in the page's filesize as reported by IE's File --> Properties screen.
matt
can you comment on my last post? i see no difference in the page's filesize as reported by IE's File --> Properties screen.
matt
0
Jeremy T. Fuller
Top achievements
Rank 1
Rank 1
answered on 23 Jun 2008, 10:07 PM
Matt,
The script and CSS combiners don't reduce the size of the download. Those resources are already "minified". The purpose of the combiners is to reduce the number of requests served. Use Firebug to compare with the combiners on and off. You'll see a drastic reduction in the number of HTTP requests to pull CSS and JS files down. The flip side of this, however, is lower client-side cache reuse, since different pages utilizing a different mixture of CSS/JS files will generate one single (but different) request, thus not utilizing your client's cache.
The script and CSS combiners don't reduce the size of the download. Those resources are already "minified". The purpose of the combiners is to reduce the number of requests served. Use Firebug to compare with the combiners on and off. You'll see a drastic reduction in the number of HTTP requests to pull CSS and JS files down. The flip side of this, however, is lower client-side cache reuse, since different pages utilizing a different mixture of CSS/JS files will generate one single (but different) request, thus not utilizing your client's cache.