i have just upgraded my computer to a Sony all in one PC and i have installed all the software i use,, but when it comes to running my application which uses infragistics controls via deployment and via Debugging environment the app crashes as soon as it has to load data into a XamDataGrid with the following error:
Argument Exception was unhandled
Item has already been added. Key in dictionary: 'Infragistics.Windows.Automation.Peers.DataPresenter.CellAutomationPeer' Key being added: 'Infragistics.Windows.Automation.Peers.DataPresenter.CellAutomationPeer'
I have tried tracking down the error but to no avail so any assistance will be greatly appreciated.
The Computer is running Windows 7 Professional 64bit and im using NetAdvantage WPF 2010.3
The issue should be addressed in the latest hotfix (available back in August). You can get the download by going to My Infragistics => Keys and Downloads.
I have tried installing the WPF 2250 Service Release but error still persists
The fix was part of that 10.3 build so it should be addressed if it were the same issue. Is it possible that your app is using a local copy of the older version? Have you verified in the Debug->Windows->Modules that bld 2250 is loaded when the problem occurs? If you still have an issue then we'll likely need a project that demonstrates the issue. Also a complete callstack of the exception could be helpful.
I am receiving a similar error "Item has already been added. Key in dictionary: 'Infragistics.Windows.Automation.Peers.DataPresenter.LabelAutomationPeer' Key being added: 'Infragistics.Windows.Automation.Peers.DataPresenter.LabelAutomationPeer'" during automation. We have several different grids throughout our product and it doesn't seem to happen on all grids only some of them.
Andrew - We are currently using version 9.1 of the XamDataGrid. Are you saying that we have to upgrade to the latest release in order for this bug to go away?
The issue only came about/surfaced when MS made some optimizations (fixes?) to the automation handling recently so we addressed the issue in all the versions still in maintenance/development at the time so 10.1 and forward. Sorry for any inconvenience but older versions were no longer being maintained at the time that the issue started.