Hello:
I'm running UltraWebGrid as part of version 10.3. We have a control where a user clicks an expand button to open an UltraWebGrid. The user types in a value, then presses a menu button to go to a different page. At that point, the application hangs. This behavior only occurs in IE 9.0.
When I turn on compatiblity view for the site, it functions fine.
What could be causing compatibility view to work but not its normal state? Would upgrading to 11.2 solve this issue? Finally, I've heard that UltraWebGrid may not be supported after the latest release - is this true?
Thanks,
Rob
Hi Rob,
In order to be able to provide any feedback I would need to see a sample where the behavior you are describing manifests.
Please note that the UltraWebGrid control is now outdated and as of .NetAdvantage 2011 Volume 2 is no longer included in our product package. I would strongly suggest that you consider switching to the WebDataGrid/WebHieararchicalDataGrid. More information regarding these controls is available at:
http://help.infragistics.com/NetAdvantage/ASPNET/2011.2/CLR4.0/?page=Web_WebDataGrid_WebDataGrid.html
Additional samples demonstrating the features of these grids can be found at:http://samples.infragistics.com/aspnet/
Please feel free to contact me if you have any questions.
Best Regards,
Petar IvanovDeveloper Support EngineerInfragistics, Inc.http://ko.infragistics.com/support
Peter:
Thanks for the prompt response. You can see a brief screencast of the behavior here: http://screencast.com/t/uF9AmLfG2A. Note that this does not happen in compatibility view.
Does Infragistics have documentation or an automated process to migrate from UltraWebGrid to WebDataGrid?
Thank you for the code and apologies for the delayed reply.
Using the code you have provided I was able to test and replicate the behavior using version 10.3.20103.1013. However using the latest service release for 10.3 - build 2217, the matter seems to be resolved. I would therefore recommend that you upgrade your product version to the latest release.
Please tell me if this helps.
Best Regards,Petar IvanovDeveloper Support EngineerInfragistics, Inc.http://ko.infragistics.com/support
Thanks for the reply. Can you send me a link to the 2217 build so I can install it?
Regards,
In order to download the latest service release you need to follow these steps:
1) Navigate to the "My Keys and Downloads" page on our website. You may be asked to log in using your Infragistics member profile's user name and password. You can reach the My Keys and Downloads page via the following link:<http://ko.infragistics.com/Membership/Default.aspx>
2) Click on the "NetAdvantage" tab. This will show all of your registered license keys for NetAdvantage.
3) Click on the license key for the product and version for which you would like to download a service release. This will bring up all available public downloads for this product and version.
4) In the "Service Releases" section, click on the link for the appropriate version of NetAdvantage. Note that there is a service release for each CLR version and in some cases a separate hot fix for an ASP.NET-only, Windows-Forms-only, WPF-only, or full installation.
Got it, thanks. Went there first but didn't look far enough down the page... sorry for the stupid question.
All should be well now.
Please do not hesitate to contact me if you have any further questions.
You are correct. I really didn't want to do it but didn't have much of a choice. I wish there was an easier way.
Thanks Rob for quick reply. That takes months to replace. Most of the code should be re-written.
Unfortuntately, no. We wound up replacing the grids with WebDataGrid.
Did you get any alternate for your problem. If yes, please let us know what you did.
Hi Peter,
Thanks. We upgraded to the latest version you recommended yet still have the problem. I have begun to implement WebDataGrid but it is an entirely different control and will require a rewrite of our grids.
I'm wondering if you can suggest another fix? It seems to only affect certain grids in IE 9.0 and I'd love to find a way to get them to work on that browser while we implement WebDataGrid.