I have found a Layout which causes the exception below:
The loaded layout was saved by calling SaveAsXML then trying to load said file. The only thing that has changed is that a large DockableControlPane was unpinned.
System.ArgumentOutOfRangeException was caught Message="Insertion index was out of range. Must be non-negative and less than or equal to size. Parameter name: index" ParamName="index" Source="mscorlib" StackTrace: at System.Collections.ArrayList.Insert(Int32 index, Object value) at Infragistics.Win.UltraWinDock.TabsCollection.Insert(Int32 index, Object value) at Infragistics.Win.UltraWinDock.UnpinnedTabArea.RemoveUnpinnedPane(DockableControlPane pane) at Infragistics.Win.UltraWinDock.UltraDockManager.PinPane(DockableControlPane pane) at Infragistics.Win.UltraWinDock.DockableControlPane.Pin() at Infragistics.Win.UltraWinDock.UltraDockManager.ControlPaneRemoved(DockableControlPane pane) at Infragistics.Win.UltraWinDock.DockableControlPanesCollection.Remove(DockableControlPane pane) at Infragistics.Win.UltraWinDock.UltraDockManager.InitializePaneControls() at Infragistics.Win.UltraWinDock.UltraDockManager.InitializeComponent() at Infragistics.Win.UltraWinDock.UltraDockManager.InitializeFrom(UltraDockManager source) at Infragistics.Win.UltraWinDock.UltraDockManager.Load(Stream stream, Boolean xml) at Infragistics.Win.UltraWinDock.UltraDockManager.LoadFromXML(String filename) at Actus2.frmWorkstation.LoadLayout(ViewType type) in C:\Documents and Settings\bjennings\My Documents\alm-actus\Release\Sprint 6\FrontEnd\Apps\Beta-Workstation\frmWorkstation.vb:line 2715 InnerException:
This looks like a bug. I would recommend submitting a sample which reproduces the issue to the support group: http://www.infragistics.com/gethelp.
I am getting the exact same error.
Is there any patch released to address the issue ?Or is it supposed to be addressed in any of the latest version (after 9.1) ?
Thanks in advance
Could you please attach if possible a small sample application which reproduces this issue for me to take a look at it and assist you further on that matter.
Hellothanks for taking the time to answer.
Unfortunately, the application is pretty big and I am not sure how to reproduce the issue in a sample application. I will try to do so and keep you posted if I succeed.
In the meantime, I was wondering if any fix regarding the same kind of issue have been addressed in ServicePack or Release version after version9.2 that I am currently using.
I have no knowing of such fixes after version 9.2, I have investigated this and could not find any. I will be waiting for your sample.