It seems that the hidden <iframe>s that Telerik's drop-down controls use (RadToolbar, RadMenu, RadContextMenu) causes performance/debugging issues when using IE and Visual Studio. We've seen this with multiple versions of IE and Visual Studio '10 and '12. We are using the latest Q2 '12 release of Telerik.
What seems to be happened is that for each <iframe>, used, say for each menu item that contains other items, IE will navigate to its internal "Cannot display web page" page:
res://ieframe.dll/dnserrordiagoff.htm
This page will also cause the load of two internal scripts (errorPageStrings.js and httpErrorPageScripts.js).
Visual Studio's Script Documents list, that exists during debugging sessions, shows this. See the first screen capture, which shows a simple test site with a single page with a single RadMenu control that has 4 drop-downs.
Aside from the theoretical performance issue of the browser constantly trying to navigate and then displaying these internal files, the real issue for us is that on our screens, we have a lot of these controls. As we debug, going from page to page sometimes takes several seconds as these spurious internal page/scripts are loaded/unloaded in the Script Documents window in Visual Studio. See the second screen capture that shows this.
So - is there anything that can be done to prevent IE from trying to navigate for these hidden <iframe>s, and thus preventing the navigate to
res://ieframe.dll/dnserrordiagoff.htm
in the first place?
Thanks,
- Mike
What seems to be happened is that for each <iframe>, used, say for each menu item that contains other items, IE will navigate to its internal "Cannot display web page" page:
res://ieframe.dll/dnserrordiagoff.htm
This page will also cause the load of two internal scripts (errorPageStrings.js and httpErrorPageScripts.js).
Visual Studio's Script Documents list, that exists during debugging sessions, shows this. See the first screen capture, which shows a simple test site with a single page with a single RadMenu control that has 4 drop-downs.
Aside from the theoretical performance issue of the browser constantly trying to navigate and then displaying these internal files, the real issue for us is that on our screens, we have a lot of these controls. As we debug, going from page to page sometimes takes several seconds as these spurious internal page/scripts are loaded/unloaded in the Script Documents window in Visual Studio. See the second screen capture that shows this.
So - is there anything that can be done to prevent IE from trying to navigate for these hidden <iframe>s, and thus preventing the navigate to
res://ieframe.dll/dnserrordiagoff.htm
in the first place?
Thanks,
- Mike
5 Answers, 1 is accepted
0
Marbry
Top achievements
Rank 1
Rank 1
answered on 08 Nov 2012, 02:44 PM
You're not the only one. I'm using the radtreeview and when I start debugging VS generates a huge list of multiple errorPageStrings.js, httpErrorPageStrings.js, httpErrorPagesScripts.js, and dnserrordiagoff.htm in the solution explorer under IE. It looks like it's generating one for each node in the tree.
It certainly slows down debugging. And I have to wonder if this is a big part of what is impacting performance in production. IE9 is faster, but it still bogs down at times with this that it really shouldn't be that stressed.
It certainly slows down debugging. And I have to wonder if this is a big part of what is impacting performance in production. IE9 is faster, but it still bogs down at times with this that it really shouldn't be that stressed.
0
Mike
Top achievements
Rank 1
Rank 1
answered on 09 Nov 2012, 01:19 PM
Marbry,
The latest release from Telerik (Q3 '12) fixes this. It also fixes the related issue with IE 10 and drop downs like RadToolbar and Radmenu - the hidden <iframe> they use no longer displays during drop down and no longer causes this bizarre script issue in Visual Studio.
Regards,
- Mike
The latest release from Telerik (Q3 '12) fixes this. It also fixes the related issue with IE 10 and drop downs like RadToolbar and Radmenu - the hidden <iframe> they use no longer displays during drop down and no longer causes this bizarre script issue in Visual Studio.
Regards,
- Mike
0
Marbry
Top achievements
Rank 1
Rank 1
answered on 09 Nov 2012, 02:14 PM
Excellent, thanks for noting that Mike. That made a huge difference in the start-up performance.
I still see a lot of "blank" items get generated when debugging, but it doesn't seem to have nearly as much of an impact.
The upgrade also went a lot smoother than last time.
I still see a lot of "blank" items get generated when debugging, but it doesn't seem to have nearly as much of an impact.
The upgrade also went a lot smoother than last time.
0
Pankaj
Top achievements
Rank 1
Rank 1
answered on 10 Apr 2013, 01:11 PM
HI,
how to upgrade my telerik version from older version to The latest release Telerik (Q3 '12)
how to upgrade my telerik version from older version to The latest release Telerik (Q3 '12)
0
Hi Pankaj,
Please refer to the following articles where you can find more detailed information on how to upgrade to the latest version of the Telerik controls:
Upgrading RadControls Trial to RadControls Developer license or newer version
Updating RadControls for ASP.NET AJAX to another version or license
Regards,
Kate
the Telerik team
Please refer to the following articles where you can find more detailed information on how to upgrade to the latest version of the Telerik controls:
Upgrading RadControls Trial to RadControls Developer license or newer version
Updating RadControls for ASP.NET AJAX to another version or license
Regards,
Kate
the Telerik team
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to their blog feed now.