Has this situation changed at all? I have an application using UltraWebGrid where customers are now using IE10 and it doesn't work. The grid displays, but poorly, and attempts to scroll or click check boxes results in an error. Setting IE to compatibility view changes the display, but does not display correctly and does not fix the scrolling error.

Converting to the WebDataGrid is not an option I'm willing to consider. We tried to use that when we first built the application, but found it so buggy that we reverted to the older UltraDataGrid. At this point, even if the bugs are fixed, the effort to convert is lengthy and costly.

Thanks

Background

I too have a project with UltraWebGrids  (v 10.2)  on several of my project pages. We are still developing using Visual Studio 2005. The Javascript behind these grids is very complex to provide client-side math computations. The .Net Framework we’re using is still 2.0. All of our clients are running under IE9. My project receives heavy use and operates very well.

I realize that IE10 is right around the corner at our facility. In fact, a few folks have inadvertently installed IE10 and, as chronicled on this excellent thread, my ultrawebgrids all went south. I’m trying to look ahead and do some planning for the inevitable. We have already been directed to upgrade our framework to 4.5 and Visual Studio to version 2012. It seems my options are as follows:

Options

1. Option 1. Upgrade to the latest version of Infragistics controls (Netadvantage for Web Client V 13.1) Replace UltraWebGrid controls with WebDataGrid. This appears to be Infragistics recommended solution, but if I have to re-create all of my Javascript code to regain my current functionality, this would be my least preferred option.

2. Option 2. I have noticed that the ugly UltraWebGrid displays encountered under IE10 can be corrected by clicking the “Compatibility Mode” icon (looks like a broken page) at the top of the page. This is an emergency fix, but not a viable long-term solution.

3. Option 3. IE10 offers a setting that allows all pages to be displayed in compatibility mode. We have not tested this option with IE10/Infragistics controls, but I believe this would be the equivalent of clicking the compatibility mode icon in the menu bar. Problem with this idea is that end users would not see the benefit of IE10 advancements while they browse pages outside of my project.

4. Option 4. The HTML statement  <meta http-equiv="X-UA-Compatible" content="IE=EmulateIE9" /> inserted right after the </title> tag on a page has solved some compatibility issues for me in the past. We have not tested to see if this statement forces the page to run in IE9 compatibility mode and allow me to continue to use ultrawebgrids successfully under IE10 or not. If this works, this may be my preferred option.

Questions

1. Does anyone know if – after upgrading to VS 2012 and Framework 4.5 – I will still be able to even build my project if I’m still using Netadvantage 10.2? Are there any special considerations?

2. Has anyone ever attempted Option 4 above?  Does it allow UltraWebGrids to display correctly under IE10?

Thanks in advance for any suggestions ….

Elizabeth -

I'm working on some proposals for future development and I want to confirm that the Javascript I created behind my existing V10.2 UltraWebGrids will have to be re-created if I replace the UltraWebGrid with the new V13.1 WebDataGrid (i.e., the JScript code does not migrate to the new control)?

Thanks for the quick response Elizabeth. We are in the beginning stages of setting up a test development platform with a VS2012 / Framework 4.5 set up. I'll attempt to build my existing NetAdvantage 10.2 project and see what happens.