Hi there...
I have set up a form that contains a number of FlyGrid controls, all of which had a few different columns set up, and all of which was working fine in the Visual Studio 2005 Pro forms designer. However, since loading my project this morning, I can no longer switch from code view to design view (I haven't tampered with any autogenerated code since it was working fine yesterday)...
Upon launching a second Visual Studio and attaching its debugger to the first instance of Visual Studio, I have tracked the problem down to an exception being thrown in the FlyGrid's disposal within the designer framework, which seems to be called whenever the form designer re-generates the form layout from the underlying code. As the FlyGrid library has been obfuscated, the following is all the information I can provide:
System.NullReferenceException: Object reference not set to an instance of an object.
at NineRays.Windows.Forms.FlyGridDesigner.lh(Object , ComponentEventArgs )
at System.ComponentModel.Design.ComponentEventHandler.Invoke(Object sender, ComponentEventArgs e)
at System.ComponentModel.Design.DesignerHost.RemoveFromContainerPostProcess(IComponent component, IContainer container)
at System.ComponentModel.Design.DesignerHost.Remove(IComponent component)
at System.ComponentModel.Component.Dispose(Boolean disposing)
at System.Windows.Forms.Control.Dispose(Boolean disposing)
at System.Windows.Forms.Form.Dispose(Boolean disposing)
at Picklefrog.AppWindowBase.Dispose(Boolean disposing) in
.... is there enough there for you guys to figurer out which method \"lh\" would map to, and perhaps suggest some reasons that a value might be null within that method? My form contains hundreds of standard winforms controls, otherwise I'd paste the offending auto-generated code here too. But I'm not doing anything using the FlyGrid that was any different to that which is shown in your tutorial videos.
Sorry I can't provide any more detail... but your reply will be appreciated - I am effectively locked out of my project until I can fix this issue.
Regards,
David.