Hello.
When I remove an item from grid I get the following exception. This is after I upgraded from Infragistics 14.2 to 15.2. I would not expect any generic exception such as a NullReferenceException to be thrown from Infragistics code, so I consider this a bug. I would try to find a workaround, but since I don't have the .pdb's or source of the Infragistics .dll's, this is a bit tricky. I've tried decompiling the related assemblies but it's not apparent where the NullReferenceException occurs.
Could you fix this bug or provide me with a workaround? Thanks
Here is the related stacktrace. Let me know if you require more information.
at Infragistics.Windows.DataPresenter.RecordManager.RemoveRecordHelper(Int32 index) at Infragistics.Windows.DataPresenter.RecordManager.OnSourceCollectionAddOrRemove(NotifyCollectionChangedEventArgs e) at Infragistics.Windows.DataPresenter.RecordManager.OnSourceCollectionChanged(Object sender, NotifyCollectionChangedEventArgs e) at Infragistics.Windows.DataPresenter.RecordManager.ProcessChangeNotification(Object sender, Object eventArgs) at Infragistics.Windows.DataPresenter.RecordManager.OnChangeNotification(Object sender, Object eventArgs, Boolean isReset, Boolean isCellChangeNotification) at Infragistics.Windows.DataPresenter.RecordManager.System.Windows.IWeakEventListener.ReceiveWeakEvent(Type managerType, Object sender, EventArgs e) at System.Windows.WeakEventManager.ListenerList.DeliverEvent(Listener& listener, Object sender, EventArgs args, Type managerType) at System.Windows.WeakEventManager.ListenerList`1.DeliverEvent(Object sender, EventArgs e, Type managerType) at System.Windows.WeakEventManager.DeliverEvent(Object sender, EventArgs args) at Infragistics.Windows.CollectionViewWrapper.OnCollectionChanged(Object sender, NotifyCollectionChangedEventArgs e) at Infragistics.Windows.CollectionViewWrapper.System.Windows.IWeakEventListener.ReceiveWeakEvent(Type managerType, Object sender, EventArgs e) at System.Windows.WeakEventManager.ListenerList.DeliverEvent(Listener& listener, Object sender, EventArgs args, Type managerType) at System.Windows.WeakEventManager.ListenerList`1.DeliverEvent(Object sender, EventArgs e, Type managerType) at System.Windows.WeakEventManager.DeliverEvent(Object sender, EventArgs args) at Infragistics.Windows.CollectionViewExtendedProxyBase.OnRootInterfaceCollectionChanged(Object sender, NotifyCollectionChangedEventArgs e) at System.Windows.Data.CollectionView.OnCollectionChanged(NotifyCollectionChangedEventArgs args) at System.Windows.Data.ListCollectionView.ProcessCollectionChangedWithAdjustedIndex(NotifyCollectionChangedEventArgs args, Int32 adjustedOldIndex, Int32 adjustedNewIndex) at System.Collections.ObjectModel.ObservableCollection`1.OnCollectionChanged(NotifyCollectionChangedEventArgs e) at System.Collections.ObjectModel.ObservableCollection`1.RemoveItem(Int32 index) at System.Collections.ObjectModel.Collection`1.Remove(T item) at OF.App.Common.EnumerableExtensions.RemoveWhere[T](ICollection`1 source, Func`2 pred) in D:\sandboxes\ALS\Source\OF.Oaf\OF.App\OF.App.Common\Util\EnumerableExtensions.cs:line 166
Regards,Remy.
I found the issue. The NuGet packages in the Infragistics 15.2 installer are outdated. They contain build 15.2.20152.2038, while the newest build is 15.2.20152.2100. Using the newest build fixed the problem for me.
Hello Remy,
Thank you for your post.
I am glad that usage of the 15.2.20152.2100 build is working to fix this issue for you. This was a known issue with 15.2.20152.2038, which was fixed for the 15.2.20152.2100 service release.
Regarding the NuGet packages being outdated, I am not seeing the same behavior you are seeing. Perhaps the NuGet file that you are pointing at in Visual Studio is pointing to a 15.2.20152.2038 one? If this is the case, I would recommend going to the directory where the NuGet packages are installed to (commonly: C:\Program Files (x86)\Infragistics\2015.2\WPF\NuGet Packages). There should be a .zip file there with the NUPKG files for 15.2.20152.2100. Extracting this and pointing your Visual Studio NuGet Package Manager at the resultant folder should resolve this out-of-date NuGet issue.
Please let me know if you have any other questions or concerns on this matter.
Sincerely,AndrewAssociate DeveloperInfragistics Inc.www.infragistics.com/support