Having used the UltraGrid control for some years now, there is something that is really bothering me. When a form containing an UltraGrid is opened by the Windows Forms Designer, VS will always perform a checkout on the form. I think I have narrowed this down the the UltraGridColumns being constantly renamed ever time the form opened (or if not every time, frequently). It is putting a numeric suffix on the grid column names (ultraGridColumn166 for example). Sometimes, simply opening the form will cause this renumbering, but I don't know why. No changes have been made to the form or the grid.
Any ideas? This is really annoying.
PS. Closing the Windows Forms designer while the UltraGrid designer "magic" is happening behind the scenes will often result in a loss of all column information. I have learned to be very careful with this, but it may be the cause of other reported issues of the type.
Thanks.
As far as I am aware, all of these kinds of issues were fixed many years ago. The post you are responding to is over 7 years old. If this is still happening in your application, then please provide us with a sample project and steps we can follow to reproduce the issue so we can see what's going on.
Hi,
now in 2021, we still have some WinForms projects that use complex UltraWinGrids to be maintained.
The reported issue is annoying us for many years and also exists with with current version of Infragistics (20.1) and VIsual Studion 2019.
Has there been any solution meanwhile which has not been reported in this thread?
We are having same problem on many windows with 'complicated' grids (20-30 columns, row layout, embedded editors etc).Opening the window in the designer causes file to become dirty, sometimes column-grouping assignment dissapears. I also noticed that sometimes columns of type System.Object and DataRelations are removed from DataSet - not sure if it's Microsoft or Infragistics serializers fault. Using 11.1.20111.2090
I would also like to be notifed on progress of CAS-81082-ZRWT57, is that possible?
Thanks for attached sample. I already create a case for you with reference number CAS-81082-ZRWT57. I`ll provide you more details about this issue through the case. Let me know if you have any questions.
Regards
I am able to reproduce the issue using your sample. There must be something different in your sample that I was not doing in mine. Maybe the containers (tab and panel), although I can't see how that could matter.
Just to be clear, what you are seeing here is a quick in the Visual Studio form designer deals with collection. You can see the same sorts of issues using other controls that support collection, like the TreeView control.
But we use a custom CodeDomSerializer to work around these kinds of issues, and so I'm not sure why it's not working here. I'm going to ask Infragistics Developer Support to create a case for you and write this up for further investigation.