Hi,
I've a localized WinForm application (default language + fr-BE).
The translation phase is my very last step in my developement cycle. But sometimes a modification need to be done afterwards. That's the moment the problems are rising.
If I change something in the form not even on the UltraGrid it happends that the ultraGridColumn variables from the .Designer.cs are renamed :
Infragistics.Win.UltraWinGrid.UltraGridColumn ultraGridColumn1 = new Infragistics.Win.UltraWinGrid.UltraGridColumn("xxx");
becomes
Infragistics.Win.UltraWinGrid.UltraGridColumn ultraGridColumn10 = new Infragistics.Win.UltraWinGrid.UltraGridColumn("xxx"); This is almost fine since it is also renamed in the default .resx file. The problem is that it is NOT renamed in the language specific fr-BE.resx file. So, my translation is DESTROYED. Could you please take a look at this problem since I'm loosing a lot of time with this ? Regards.
Infragistics.Win.UltraWinGrid.UltraGridColumn ultraGridColumn10 = new Infragistics.Win.UltraWinGrid.UltraGridColumn("xxx");
This is almost fine since it is also renamed in the default .resx file.
The problem is that it is NOT renamed in the language specific fr-BE.resx file.
So, my translation is DESTROYED.
Could you please take a look at this problem since I'm loosing a lot of time with this ?
Regards.
What version of the controls are you using?
The Form Designer in DotNet does not handle collections well and this is a common problem with controls that use collections. You will see the same kinds of issues with the inbox TreeView control.
Having said that, we have worked around several common issues in our controls, including the grid. And what you are describing here looks like something we fixed a while ago. So you may need to get the latest service release.
How to get the latest service release - Infragistics Community
If you cannot do that, then I recommend setting your localized strings at run-time instead of in the designer to avoid these kinds of issues.
Thanks for the answer.
I'm using version 2010 Vol. 1
I'm not sure if the issue you are having is fixed in that version, but you could try download the latest Service Release and see if that helps.
If not, you could consider upgrading to a newer version of NetAdvantage. But I'd try download the trial version first and see if it works okay.
The best advice I can offer you is to preform these operations are run-time. That's really the only sure way to make sure it works and will continue to work due to the quirkiness of the Form Designer.
Hello pvdbpvdb,
Did you have the time to try downloading the latest service release available for v10.1 or the trial version of NetAdvantage 11.2 and test your application against it? Please let us know if you need additional help.