- NetAdvantage 2014.2 (also happened in 2013.1 before upgrading)
- .Net 4.5
- Visual Studio Professional 2013
I'm trying to design a grid in a standard WinForms application. I was able to set the look of it and add the initial set of columns just fine, but after a while it started misbehaving. The changes I made in the designer (most notably columns and summaries) were frequently not being saved to the form's designer file (MainForm.Designer.vb), which led to the designer reloading the old settings once I built the application.
This doesn't happen with the standard .Net controls added to the form, and the ultrawingrid is the only Infragistics control I use in this project.
For a little while it seemed like I could get around it by clearing the contents of licenses.licx, but that has also stopped working now. I can now successfully get it to update the designer file once every 10-20 attempts, which gets really annoying really quickly.
Any suggestions about why this is happening? This project is pretty much dead until I can finish designing this grid, so I hope there's a solution. Thanks!
Hi Sindre,
Thank you for posting in our forums.
This is very strange since the changes should be persisted to the design file without the need to do anything on your side. I will need additional details in order to help you resolve this issue. Have you installed any add-ins or extensions for your Visual Studio recently? Please try to create a new empty WinForms project and add an UltrGrid to it. Then try to set some of the properties in design time and let me know if this works.
Also please see if any exceptions aren’t being thrown when you are editing the grid in design time in your application. You can check this by opening your application in one instance of Visual Studio and then opening a second instance of Visual Studio. Then in the second instance open the “Attach To Process” window from the Debug menu. Select the first instance of the Visual Studio and set the second instance to break on all exceptions (Debug -> Exceptions… -> check the Thrown checkbox for Common Language Runtime Exceptions). Then try to edit some settings for the UltraWinGrid in design time, build the application and see if there are any exceptions being thrown.
I am looking forward to hearing from you.
Thanks for replying, Dimitar!
- Have you installed any add-ins or extensions for your Visual Studio recently?
No. I installed the latest service release a week ago, but this problem started before that.
- Please try to create a new empty WinForms project and add an UltrGrid to it. Then try to set some of the properties in design time and let me know if this works.
I can't seem to recreate the problem in a fresh project, at least not after a few tries. Not sure if that means it's contained in the current project, or if it's triggered by some specific property setting there.
I also tried copying and pasting the grid from the problematic project to the new one, and after 3-4 attempts I was not able to reproduce it that way either. I'll keep trying to mess with it and post again if I get a different result.
- Also please see if any exceptions aren’t being thrown when you are editing the grid in design time in your application. You can check this by opening your application in one instance of Visual Studio and then opening a second instance of Visual Studio. Then in the second instance open the “Attach To Process” window from the Debug menu. Select the first instance of the Visual Studio and set the second instance to break on all exceptions (Debug -> Exceptions… -> check the Thrown checkbox for Common Language Runtime Exceptions). Then try to edit some settings for the UltraWinGrid in design time, build the application and see if there are any exceptions being thrown.
I attached it and was able to reproduce the problem. However, the output window of the new Visual Studio window doesn't show any exceptions being thrown in the problematic instance.
If it looks like the copy-pasted grid is behaving correctly in a new project, I might just bite the bullet and move all my code and my other forms over to a fresh project, and then copy-paste the grid manually to see if I can get rid of whatever is causing this.
Thank you for the provided sample.
I have investigated your issue and, I have asked our engineering staff to examine this further. To ensure that it will receive attention, I have logged this behavior in our internal tracking system and I have opened a private case for you - CAS-159358-S2H0X3. You can view your currently active cases from this link:
https://www.infragistics.com/my-account/support-activity
Hi Dimitar!
I was just wondering if you know how long I can expect it to be before anyone looks at this case? If it's going to take much longer I'm going to have to rebuild my application with another grid component. The customer can't wait for this project much longer, and I can't be stuck with a project that's basically impossible to maintain as it stands now.
Thanks!
The issue is currently being reviewed by our developers and I can’t give you a timeframe when it will be fixed. Please see my response in the private case for more details.
We're running into this problem too and it's been very annoying. Eventually the properties do "stick" in the designer file, but there appears to be no obvious trigger than makes it work or not work. Hopefully this will be fixed soon.
Matt
Hi Matt,
This issue has been now resolved and it is scheduled to be released in our December service release. For more information on our release schedule, please visit this page:
http://www.infragistics.com/support/service-releases
Please let me know if you have any additional questions.