Hello all,
is it possible to use Infragistics Controls under Visual Studio 2010? if yes, which version?
In moment I am using Infragistics V8.3, it seems that it does not work...
Many thanks in advance!
Best regards
I'm running into the same issue.
Infragistics states they are ready to help you, but the win form controls do not work. I put a MDI dock manager and toolbar manager on a form, save and close the form, then reopen the form and i get all kind of errors: Duplicate component name '_Form1_Toolbars_Dock_Area_Left'. Component names must be unique and case-insensitive. And i have yet to see any posting about this. I know its not my machine, i just recieved a brand new laptop and the first thing i did was install VS2010 and Winform 2009.2.
I am having a similar issue with using the ultraDockManager and very simple layout of four (4) controls. I am wondering if you every had any resolution to this issue.
We are using Infrgistics2 v9.2 running in VS 2010 Beta 2 and our target is .NET Framework 4
We removed all references to the ultraDockManager in the Designer.cs file of our window form, and the form came back in the VS Designer. We then added the ultraDockManager back, step-by-step, everything looked great. When we closed the solution and opened it again, we get errors in the designer.
The errors are as follows:
Duplicate component name '_gnomonMainFormUnpinnedTabAreaLeft'. Component names must be unique and case-insensitive.
We get the above line for TabAreaRight, TabAreaTop, TabAreaBottom, and an additional one AutoHideControl.
Once this happens, we can no longer use our form in the designer.
Please help as we are having difficulty proceeding with development.
ThanksPhil
Hi,
As I mentioned in a previous post in this thread, this is a confirmed bug in the beta from Microsoft in the Windows Forms designer. It will be available in the next public release from Microsoft. Unfortunately, we don't have a date, but we do know the issues are addressed.
Let me know if I can help out any further,
Jason
Jason,
Thanks for your reply. I did see your previous message, and understand the designer is having difficulty (auto)generating Begin/EndInit method calls. I guess what is unclear, to me at least, is which of the IG components are affected by this bug in VS 2010? I mean, if I obviate the use of the UltraDockManager, for the time being, with some other set of components, how will I know this same issue won't affect those components?
Any insight would be appreciated.
Thanks.Phil
Sorry about that, I have been living this so I made an assumption.
So far, I have had reports of Tab, Toolbars and DockManager. I just spoke with the Dev Lead and this will affect any of our controls that implement ISupportInitialize, which is near half of what we ship in the box.
Let me know if I can look into anything else,
Thanks