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
pramanju,
You will need to update the references on all of your projects with the new key value if you are compiling with a different key. We will not be able to provide you with the key that we use to sign our assemblies. The other option would be to upgrade all your projects to the later version of our tool set and for this you could use the Version Utility to update the references of your projects.
Let me know if you have any questions with this matter.
Andrew, in case of strong name, the dlls are expected to be signed with public key 7dd5c3163f2cd0cb. If we use our .snk file to strong name then we are running into compilation issues because of mismatch in public key .Our existing binaries which have references with above key not able to detect the compiled binary with different strong name. This is resulting into too many changes in our projects to remove the old dll reference and add the new compiled binary which is affecting QA delivery. We have around mroe than 200 projects in the suite.
Is there anyway I can get .snk file you guys used to strong name your assemblies? In that way we will make sure that the binaries contains public key which depandant binaries are expecting. Let me know any work around for this.
I can't really give you a definitive answer. As you see that method is that of the WPF AutomationPeer class and it is used to obtain the list of direct child automation peers for a given automation peer. WPF determines when those classes are created and it invokes those methods. The automation peers are usually created because some automation/accessibility client is requesting information about the application. If you want to test the automation classes one typically uses something like UISpy or UIAVerify or other automation testing tools but other automation clients (e.g. assistive technology tools, screen interaction recording tools, etc.) would likely cause the peers to be created as well.
Alan,
Our testing groups are really concerned as the Infragistics grid is being used all across the product suite. Can you tell us when and where the GetChildrenCore method gets called so that we can advise them accordingly?
Those steps look correct if you need strong named assemblies.