I keep getting the following error message when I run my application. It matters not if I select Yes or No, it keeps appearing. At some point in time it will stop. How do I make it really go away?
A little more info might be helpful...
This dialog appears BEFORE any UI from my application but does not block my application from running. I can either move the first screen out of the way and click on either <yes> or <no> to make it go away, or wait until I am done running my program to deal with it.
This also happens on my another developers machine who has never modified any of my code. He is simply building the code, running to make sure it runs, and then pulls out all the user controls and other assemblies into the bigger project. This dialog does NOT appear when he uses my code in the bigger project.
It looks like it is a Visual Studio issue dialog, not something coming from my application.
Sam
Hi Sam,
This dialog should only show up at design-time, it should show up at run-time.
My first guess is that you are using an older version of the tree and that this is a bug that was fixed a long time ago. So I recommend that you get the latest service release and see if that helps:
How to get the latest service release - Infragistics Community
I just got done rebuilding my machine from scratch because of this issue and a few others issues. This issue is back. What is the definition of "older version of the tree"?
I am using NetAdvantage_WinForms_20091.exe, aka 2009 vol 1
Yesterday, after the rebuild, everything was fine. I was able to go in and make non UI changes and the dialog never appeared. Just now I went into a UI that has a dockManager and a lot of other controls (see attached screen shot below). All I did was wire up data binding on the name of the ultraGrid that is circled in the screen shot. I am now getting the error message and when I click on either Yes or No, Visual Studio crashes!
Hi,
I'm afraid I am at a loss to explain this.
The prompt you are getting indicates that the DataSource (or DataMember) property of the UltraTree has been changed and the current ColumnSets may be invalid. This message should only ever appear at design-time and only when these properties change.
Perhaps something in your application is causing the DataSource to change for some reason. Although I can't see how binding the grid would have anything to do with it.
You can turn off the automatic generation of ColumnSets by setting tree.ColumnSettings.AutoGenerateColmunSets to false. But then you will need to generate the ColumnSets yourself. Or perhaps set this property back to true in the form's constructor (after the call to InitializeComponent).
All of this is, of course, just a workaround and doesn't really address the issue.
Are you able to duplicate this in a small sample project you could post here so we can try it out?
Mike,
I don't think I could reproduce this problem very easily. For one thing, Visual Studio isn't crashing anymore. I changed something, don't know what, I am changing a lot of code all over the place, but something has changed and Visual Studio doesn't crash now. The dialog still appears, but no crash.
Computers are, well, their won creatures, anyone that thinks we actually control them is fooling themself.
I am always data binding all container controls to BindingList of custom written objects. I am never binding an Infragistics control to either a DataTable nor UltraDataSource. What impact would it have on me if I did turn off AutoGenerateColumnSets?
And is that a system wide switch? How do I turn it off?
I know what you mean.
There's not much more I can do at this point without being able to duplicate the issue. For a problem like this, you probably won't be able to create a new project and build up to it. So I'd recommend taking the opposite approach. Make a copy of your real application and then start removing pieces of it one at time until you've narrowed it down. If you can post a sample of a reasonable size that I can run here without having to access your data source, then I can take it from there.
If you just want to move on with your project without spending any more time on this, then I'd recommend trying the workaround for now. Turn off AutoGenerateColumnSets at design-time, and then switch it on at run-time in the form constructor and see if that helps.