I would love to decrease the number of exceptions that the debugger is encountering in the XamDataGrid.

I expect that these happen only when a number of factors are in play, and they only affect the debugger in a serious way when I disable "Just My Code" in VS 2015.

Basically here is how to recreate:

• Bind to ADO.Net dataset in VM layer
• Edit some data and scroll it out of view in the grid
• In my VM layer I clear the ADO.Net dataset and accept changes

The exceptions that happen seem to be a result of an asynchronous refresh operation in the xamdatagrid (in FlatScrollRecordsCollection, to be exact):

  InfragisticsWPF4.DataPresenter.v15.2.dll!Infragistics.Windows.DataPresenter.FlatScrollRecordsCollection.RaiseCollectionChangedHelper(System.Collections.Specialized.NotifyCollectionChangedEventArgs eventArgs) Unknown
  InfragisticsWPF4.DataPresenter.v15.2.dll!Infragistics.Windows.DataPresenter.FlatScrollRecordsCollection.RaiseChangeEvent(System.EventArgs e, bool async) Unknown
  InfragisticsWPF4.DataPresenter.v15.2.dll!Infragistics.Windows.DataPresenter.FlatScrollRecordsCollection.RaisePendingNotifications() Unknown

This "RaisePendingNotifications" comes along to the front of the Dispatcher and it is presumably going to clear out my records from the U/I.

But I end up getting a TON of first-chance exceptions from GetCellValueHelper in DataPresenter.DataRecord like so:

GetCellValue failed, exception type: System.Data.RowNotInTableException, exception msg: This row has been removed from a table and does not have any data.  BeginEdit() will allow creation of new data in this row., item index: 8, DataItem: System.Data.DataRowView

I assume the XamDataGrid is not happy about the missing record data with DataRow entries that are no longer attached to a table (or maybe it is not happy working with ADO.Net bindings in general).

I've attached the full stack when encountering the RowNotInTableException.  Note that the repro would be difficult to give you because of several factors:

• Only ADO.Net issue (clear based on Exception)
• Only a significant debugger performance issue if I disable "Just My Code"
• (although it probably affects performance to a degree either way)
• Only seems to occur when I scroll records in and out of view on the xamDataGrid
• Maybe additional factors...

I'd love to find a better way to keep the xamDataGrid "in step" with the changes to the data in the VM (ie in the VM layer I clear the ADO.Net dataset and accept changes)

Is there some straightforward way I can clear my old data *without* cause all the unnecessary overhead of async exceptions (which happen when the xamDataGrid attempts to bring itself back in sync)?  Can I create an interface/callback to the xaml view and unbind temporarily, or clear DataRecords manually, or something of that nature as a workaround?  Anything like that would be worth doing, as far as I'm concerned.  I'm open to ideas.  I'd like to stay with ADO.Net if possible.

Please let me know if there are any thoughts about a workaround.