We recently updated our Infragistics NetAdvantage WPF install to version 11.1.20111.2173 and started getting the exception below on all our xamDataGrids.
The previous version (11.1.20111.2053) didn’t have this issue. That attached sample app will get this error when using version 11.1.20111.2173 and works fine with version 11.1.20111.2053. Please let me know if there is a fix/workaround for this issue.
{"Object reference not set to an instance of an object."}
at Infragistics.Windows.DataPresenter.Internal.TemplateDataRecordCache.InitializeCachedCellArea()
at Infragistics.Windows.DataPresenter.Internal.TemplateDataRecordCache.VerifyCache()
at Infragistics.Windows.DataPresenter.Internal.TemplateDataRecordCache.GetCellValuePresenter(Field field, Boolean createIfNull)
at Infragistics.Windows.DataPresenter.CellTextConverterInfo..ctor(Field field)
at Infragistics.Windows.DataPresenter.CellTextConverterInfo.GetCachedConverter(Field field)
at Infragistics.Windows.DataPresenter.RecordManager.SameFieldRecordsSortComparer.FieldSortInfo.Initialize(FieldSortDescription fieldSortDescription, SameFieldRecordsSortComparer comparerInfo, FieldLayout fieldLayout)
at Infragistics.Windows.DataPresenter.RecordManager.SameFieldRecordsSortComparer.FieldSortInfo..ctor(FieldSortDescription fieldSortDescription, SameFieldRecordsSortComparer comparerInfo, FieldLayout fieldLayout)
at Infragistics.Windows.DataPresenter.RecordManager.SameFieldRecordsSortComparer..ctor(FieldLayout fieldLayout, Int32 recordsBeingSortedCount, Boolean areRecordsInUnsortedOrder)
at Infragistics.Windows.DataPresenter.RecordManager.SortHelper(Record[] records, Boolean hasGroupByFields, Boolean& hasMultipleFieldLayouts, Boolean areRecordsInUnsortedOrder)
at Infragistics.Windows.DataPresenter.RecordManager.VerifySort()
at Infragistics.Windows.DataPresenter.RecordManager.OnSourceCollectionReset()
at Infragistics.Windows.DataPresenter.RecordManager.PostDelayedReset()
at Infragistics.Windows.DataPresenter.RecordManager.SetDataSource(IEnumerable currentValue, Boolean postReset)
at Infragistics.Windows.DataPresenter.RecordManager.set_DataSource(IEnumerable value)
at Infragistics.Windows.DataPresenter.DataPresenterBase.VerifyRecordManagerDataSource()
at Infragistics.Windows.DataPresenter.RecordManager.VerifyRootDataSource()
at Infragistics.Windows.DataPresenter.RecordManager.get_Sorted()
at Infragistics.Windows.DataPresenter.RecordManager.get_Current()
at Infragistics.Windows.DataPresenter.DataPresenterBase.get_RecordManager()
at Infragistics.Windows.DataPresenter.DataPresenterBase.OnInitialized(EventArgs e)
at Infragistics.Windows.DataPresenter.XamDataGrid.OnInitialized(EventArgs e)
at System.Windows.FrameworkElement.TryFireInitialized()
at System.Windows.FrameworkElement.EndInit()
at MS.Internal.Xaml.Runtime.ClrObjectRuntime.InitializationGuard(XamlType xamlType, Object obj, Boolean begin)
at System.Xaml.XamlObjectWriter.Logic_EndInit(ObjectWriterContext ctx)
at System.Xaml.XamlObjectWriter.WriteEndObject()
at System.Xaml.XamlWriter.WriteNode(XamlReader reader)
at System.Windows.Markup.WpfXamlLoader.TransformNodes(XamlReader xamlReader, XamlObjectWriter xamlWriter, Boolean onlyLoadOneNode, Boolean skipJournaledProperties, Boolean shouldPassLineNumberInfo, IXamlLineInfo xamlLineInfo, IXamlLineInfoConsumer xamlLineInfoConsumer, XamlContextStack`1 stack, IStyleConnector styleConnector)
at System.Windows.Markup.WpfXamlLoader.Load(XamlReader xamlReader, IXamlObjectWriterFactory writerFactory, Boolean skipJournaledProperties, Object rootObject, XamlObjectWriterSettings settings, Uri baseUri)
at System.Windows.Markup.WpfXamlLoader.LoadBaml(XamlReader xamlReader, Boolean skipJournaledProperties, Object rootObject, XamlAccessLevel accessLevel, Uri baseUri)
at System.Windows.Markup.XamlReader.LoadBaml(Stream stream, ParserContext parserContext, Object parent, Boolean closeStream)
at System.Windows.Application.LoadComponent(Object component, Uri resourceLocator) at XamGridTest.MainWindow.InitializeComponent()
Hello Samuel,
I contacted our Release team, and it turns out that the Service Release is ready and will be available for downloading until the end of this week.
Thank you for your patience.
Hi
I've got the same problem, the service release should be available since 5 days. Can you please publish the release?
Thanks
Samuel
Hello,
Thank you for your post. I have been looking into your sample and I was able to reproduce your behavior. I also tested you sample with the latest internal build of 11.1 and there it was fixed, so I suggest you wait till January 20th when a service release is planned according to this table:
http://ko.infragistics.com/support/service-releases.aspx#ServiceReleases
Please let me know if this helps you or you need further clarifications on this matter.
Looking forward for your reply.