Mohandas,

Please provide a sample that replicates how you are setting up the grid in your application that I can run and debug to find out what is happening.  There is relevant logic that isn't included in the code that you have already provided and this will allow me to help you faster.

Let me know if you have any questions with this matter.

Mohandas,

I recommend starting a new thread for your issue with a sample that reproduces the issue.  I did look at your code and see that you are adding the sorting behavior to the child band though none of your markup is included or the definition of the parent columns.  Some things that come to mind that could cause behaviors to fail in general:

• DataKeyFields aren't set correctly so the children aren't found.
• As the behavior is added dynamically, it needs to be added on every call to the server and for this it would be better to set up the behaviors in markup.

Let me know if you have any questions with this matter.

Allan,

2005 Volume 3 was released in late 2005 and was supported in IE 6 as that was the current version of IE at the time.  IE 11 was released in 2013 so the older version of our toolset was never tested or supported in the much newer version of IE.

IE 11 support was added our 2013 Volume 1 release.  Note that the UltraWebListBar is among the controls that were retired after the 2011 Volume 1 release and if you want to use a version of our ASP.NET toolset that does support IE 11, you would need to switch the control used to the WebExplorerBar.  There are more details on what controls were retired and their replacements in the classic control migration guide in the documentation.

Note that if you need support for modern browsers including Chrome, Safari, Edge, current versions of IE, and current versions of Firefox, it may be better to rewrite the application with with a modern web framework and our client side Ignite UI toolset.

Let me know if you have any questions with this matter.

Allan,

In compatibility mode, IE is probably sending a user agent string that is reporting a version of version of IE that is less than 10 so the exception doesn't occur when in compatibility mode.  If this doesn't happen in production and only in staging then for some reason based on browser settings your production site is probably also running under compatibility mode.  I recommend reviewing your compatibility view settings to see what sites run in compatibility view and note that there is an option to run intranet sites in compatibility view..

Let me know if you have any questions with this matter.

Allan,

I believe the exception you are seeing has to do with logic that parses the browser version and was fixed in a later version of the toolset for firefox 10 which was released in early 2012 so you will need to get the latest service release of 2011 Volume 1 to get the fix for this.  The bug would impact any browser that has a version of 10 or greater.

Hello,

Thank you for posting the resolution, I am glad to hear that it is now working.

Hello,

The exception is happening in the constructor of the form so you might be able to put a break point there.  It is possible that even with these settings if the debug symbols aren't available that the code is still skipped over. 

The exception details are showing that it can't load either version of the assembly.  In your initial post, you mention that you have both versions on the system so I assume that these aren't in the GAC on the machine or in the bin directory of your application.

What are the contents of the bin directory when the applications is compiled are the Infragistics references there?  If yes, is the Infragistics2.Win.v11.1 assembly there?  If no, do you expect them to be (or are you loading them from the GAC)?

If they are missing and you expect them to be in the bin directory, changing "Copy Local" to true on the references will put them there when you compile the application.

If they aren't in the GAC, what version is there? If any?

Sincerely,
Alan Halama
Support Architect