Hi,
I have binded a collection with xamdatagrid in which there is a delete button to delete the records by passing selected row index in command parameter. The strange thing is that the functionality was working fine while we were using Infragistics dlls 11. 2 version. But there is ''Object reference not set to an instance of an object'' exception is coming from when new Infragistics dlls 15.2 version updated. Following details of exception are
at Infragistics.Windows.DataPresenter.RecordManager.RemoveRecordHelper(Int32 index) at Infragistics.Windows.DataPresenter.RecordManager.OnSourceCollectionAddOrRemove(NotifyCollectionChangedEventArgs e) at Infragistics.Windows.DataPresenter.RecordManager.OnBindingListChanged(Object sender, ListChangedEventArgs 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.DeliverEvent(Object sender, EventArgs args, Type managerType) at System.Windows.WeakEventManager.DeliverEvent(Object sender, EventArgs args) at Infragistics.Windows.Helpers.BindingListChangedEventManager.OnListChanged(Object sender, ListChangedEventArgs e) at System.ComponentModel.BindingList`1.OnListChanged(ListChangedEventArgs e) at System.ComponentModel.BindingList`1.FireListChanged(ListChangedType type, Int32 index) at System.ComponentModel.BindingList`1.RemoveItem(Int32 index) at System.Collections.ObjectModel.Collection`1.RemoveAt(Int32 index)
Thanks
Sonia
I upgraded to the latest version and I face this issue. Is there a fix for it yet?
Here is my stack trace
System.NullReferenceException: Object reference not set to an instance of an object. 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 System.Collections.Specialized.CollectionChangedEventManager.OnCollectionChanged(Object sender, NotifyCollectionChangedEventArgs args) at System.Collections.Specialized.NotifyCollectionChangedEventHandler.Invoke(Object sender, NotifyCollectionChangedEventArgs e) 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)
Thanks!
The support told me that the fix will be included in the next service release.
This seems like a terrible bug to just leave hanging until the next service release. Will Infragistics consider accelerating the next service release or providing an out-of-band hotfix?
All,
We do have this fixed internally and the fix will be in the next service release that is expected to be released in March according to the service release schedule. If this is too long to wait, we do have a patch for 2015 Volume 1 and 2015 Volume 2 available that we have run our automated testing on though haven't done the additional manual testing that we do for a service release:
Let us know if you have any questions.
Hello,
The development issue with ID of 211278 has been fixed and it is available in the latest Service Release. You can download the Service Release by logging in our web site and then going to Account\My Keys and Downloads page.
Thank you for using Infragistics Components.
Sincerely,
Teodor
Software Engineer
Infragistics
www.infragistics.com/support
we had the same Problem. The inofficial patch solved it, thanks!
BR Florian
My team tried the 2015 Volume 2 Patch, and still getting the same error. Will this issue persist in the next service release?
Martin,
If the errors are caused by something else, please provide more details so that we may assist you.
Hi Martin,
The most likely reason for your namespaces breaking is because your application was upgraded to 15.2 from an older version and you had xml namespaces like this:
xmlns:igDV="clr-namespace:Infragistics.Controls.Charts;assembly=InfragisticsWPF4.DataVisualization.v15.2"
At the end of this namespace is the specific volume release the assembly belongs to. If you came from an older version this number will be different. Upon upgrading, if you did not change the assembly version # at the end of the namespace then you are going to get errors.
To keep this from happening in the future, please use the generic namespace urls:
xmlns:ig="http://schemas.infragistics.com/xaml"xmlns:igWPF="http://schemas.infragistics.com/xaml/wpf"