Hi, we are experiencing some issues in design mode in many of the forms. Every time we open the form in Designer it requests for Check-out from TFS and changes the table definition, remaining the same but with different column names in designer. We use collections as datasource in design time for grids.
For example,
the first time we create a form it creates Ultragridcolumn1 and Ultragridcolumn2 in designer.vb.
Next time we open removes both columns and create Ultragridcolumn3 and Ultragridcolumn4, asking for Check-out and increasing the risk of accidentally modifying anything, apart of the annoying thing of having to check-out an prevent other users to work with that form.
Any help would be appreciated.
Regards
Hi, What version of the grid are you using? This sounds like an issue that was fixed.
You might just need to get the latest service release.
How to get the latest service release - Infragistics Community
Version 10.3.20103.1000
Which of the issues are you talking about?
I was referring to the issue of the names of the column variables changing.
I do not understand what you are describing in your second post here.
Hi,
I just wanted to know if you were able to solve your issue based on Mike’s suggestions or you still need help? Just let me know if you need nay further assitance on this.
Thank you.
theabdabs said: 1. Open form in Design View 2. Debug the application (form remains opened in VS IDE) 3. Finish debugging and try to edit the form in Design A SystemComponentException is shown. Need to close the form and open it again in Design. Sometimes it gets opened, sometimes need to restar VS
1. Open form in Design View
2. Debug the application (form remains opened in VS IDE)
3. Finish debugging and try to edit the form in Design
A SystemComponentException is shown. Need to close the form and open it again in Design. Sometimes it gets opened, sometimes need to restar VS
I'm not aware of any issues that could cause something like that. Unless maybe you are using multiple versions of the same assemblies or CopyLocal is set to true on some of them.
If you can post the Call Stack of the exception, maybe it will give us some clue.
In the second post I mean.
About the first issue, I'm checking if we're running the latest version, as the last source code available to download has an earlier version than the one we are running.
Many thanks for you help