Error in designer code generation

Hi, I''m getting the following error message after modifying a form containing a Essential Grid: Code generation for property ''RowHeightEntries'' failed. Error was: ''Key cannot be null. Parameter name: key'' Code generation for property ''ColWidthEntries'' failed. Error was: ''Key cannot be null. Parameter name: key'' Code generation for property ''ColHiddenEntries'' failed. Error was: ''Key cannot be null. Parameter name: key I''m using Essential Suite version 3.0.1.1, but the forms were already created with earlier versions. Any help? Regards, Holger Persch

Try this. Before modifying the old form, click the grid on the design surface, and then click the Touch It verb under the grid''s propertygrid. Next close the form in the designer. Then reopen the form and try to make your change.

It doesn''t help. After clicking the "Touch it" link the form gets modified and I need to save before closing it. During saving, when the "InitializeComponent" code is rewritten, the errors are appearing again. Another question: What is the funtion behind the "Touch it" link? Regards, Holger Persch

Here is the code behind the Touch It verb in the GridControlDesigner class (which is internal). It just triggers a rewrite of the code. private void OnTouchAndSave(object sender, EventArgs args) { GridControlBase grid = this.Control as GridControlBase; if (grid != null) { IDesignerHost host = this.GetService(typeof(IDesignerHost)) as IDesignerHost; this.BroadcastComponentChanged(); grid.Invalidate(); } } As far as the error, did you run the ConvertResx utility to move these 2.x resx files up to 3.0.1.0?

Holger, this sounds like a bug in the ColWidthEntries and RowHeightEntries collection that must be somehow related/triggered by the the original data from the resx file. Can you send us the resx file - we can then try to create a small sample that tries to load and convert it. Or if you have a sample project that worked in 2.x and now gives you trouble with converting the resx that would be even better. Thanks, Stefan

There seems to be a problem with uploading files to your site. I''m not able to upload the resx file, neither in the forum nor in DirectTrac. Regards, Holger Persch

File upload works now. I attached a resx file containing a grid that produces these errors. Regards, Holger ExplorerDynamicRelationTypesView_2774.zip

Any news here? Should I create a DirectTrac incident? Regards, Holger

Holger, The resx didn''t give much clues so far. It looks like you are actually not doing any formatting for the grid that is stored in the form, correct? How do the lines of code in your form look like that initialize the grid. Are there any code statements that try to initialize ColWithEntries, RowHeightEntries etc? Right now my guess is that you somewhere in your form have statements like this: resources.GetObject("gridControl.RowHeightEntries") and that fails then. Could that be it? Do you also have the old resx file before it was converted to 3.0.1.1? Stefan

Hi Stefan, I''m sorry the resx file I attachted here doesn''t contains formating code because it''s from an inherited user control and all the fomatting is done in the base control. I now have attached two resx files, a non converted file (pre 3.0.1.1) and a converted file. Hope this helps. I searched for the "RowHeightEntries" statement in all code files. I found out that all the forms and controls, containing a grid that produces these errors, doesn''t contain statements like this. All forms that are working well do contain this statement. How can we proceed? Regards, Holger ExplorerGridView_926.zip

Hi Holger, your old resx does not contain any entries for the RowHeights, ColWidths, HideCols nor HideRows (that''s how row heights and column widths were persisted prior to 3.0). Therefore, there should be no row height entries and column width entries be generated for your form. I don''t understand why these collection are created in your case (it is really hard to find out without a sample project). What I suggest it you simply delete those lines from your form that cause problems after you converted the form since you have no custom row heights / column widths in your grid. Stefan