We just changed our version of Infragistics from 10.2 to 10.3 and we are running into some issues with them. We have narrowed the issues down to the new assemblies, and I have included the error messages below. It seems to happen on any page that contains an Infragistics control, but it only happens on 3 of our 10 development systems. We have tried many different things to try and get this to work properly. The project builds, and runs, but when navigating to a view which contains an Infragistics control the below errors are displayed.
I have tested this in several browsers as well on all of our machines.
User Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; MS-RTC LM 8; .NET4.0E; .NET4.0C)Timestamp: Mon, 14 Nov 2011 17:59:00 UTCMessage: Unhandled Error in Silverlight Application Code: 4004 Category: ParserError Message: Set property 'Infragistics.Controls.Commanding.Command' threw an exception. File: Line: 1097 Position: 72 Line: 56Char: 13Code: 0URI: http://localhost:3988/Login.aspxMessage: Unhandled Error in Silverlight Application Code: 4004 Category: ManagedRuntimeError Message: System.ArgumentException: Object of type 'Infragistics.Controls.Grids.XamGridColumnCommandSource' cannot be converted to type 'Infragistics.Controls.CommandSource'. at System.RuntimeType.TryChangeType(Object value, Binder binder, CultureInfo culture, Boolean needsSpecialCast) at System.RuntimeType.CheckValue(Object value, Binder binder, CultureInfo culture, BindingFlags invokeAttr) at System.Reflection.MethodBase.CheckArguments(Object[] parameters, Binder binder, BindingFlags invokeAttr, CultureInfo culture, Signature sig) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at MS.Internal.XamlMemberInfo.SetValue(Object target, Object value) at MS.Internal.XamlManagedRuntimeRPInvokes.SetValue(XamlTypeToken inType, XamlQualifiedObject& inObj, XamlPropertyToken inProperty, XamlQualifiedObject& inValue) Line: 56Char: 13Code: 0URI: http://localhost:3988/Login.aspx
Any and all help is appreciated with this problem because it is impeding our development ability currently.
Thank you.
This has now been solved. What was happening is the computers that actually had Infragistics 10.2 installed on their machines where the ones having issues. For some reason VS was retrieving the 10.2 and 10.3 dlls and building them into the xap file for the Silverlight modules which was causing the conflict when the grid was loading between the two commanding types.
To resolve this issue the ClientBin folders were emptied, and Infragistics 10.2 was removed from the computers.