Do u have the list of bugs fixed in v2018.2 and v2019.1?
We need to make a decision on whether we should upgrade to latest version. Currently in our product we have v2018.1 and heavily using WPF XamGrid & XamComboBox.
Thanks,Gajender
Hello Gajender,
After each service release, we create a blog post where you can download a list of bug fixes that happened for that particular service release. As version 2019.1 has not received a service release yet, it is essentially on the same level as the most recent service release for 2018.2, but it has the features that were in 2019.1 and not in 2018.2. Here are the links for the service releases for 2018.2:
- https://www.infragistics.com/community/blogs/b/engineering/posts/infragistics-ultimate-ui-for-wpf-release-notes---november-18-2-volume-release
- https://www.infragistics.com/community/blogs/b/engineering/posts/infragistics-ultimate-ui-for-wpf-17-2-18-1-18-2-service-release-notes---december-2018
- https://www.infragistics.com/community/blogs/b/engineering/posts/infragistics-ultimate-ui-for-wpf-18-1-18-2-service-release-notes---april-2019
It is also worth noting that we highly recommend that you begin migrating to the XamDataGrid control from the XamGrid if you haven't already. As it states in our online documentation for the XamGrid, here: "We recommend that you use the XamDataGrid control instead of the XamGrid control. The XamGrid is being planned for retirement over the next few years and will not receive any new features. We will continue to provide support and critical bug fixes for the XamGrid during this time."
Please let me know if you have any other questions or concerns on this matter.
Does it mean XamGrid control will no longer be available after few years and we will be forced to converter all XamGrid controls to XamDataGrid controls meanwhile?
The XamGrid will likely not be completely removed from the Infragistics for WPF toolset as the XamGantt and XamPivotGrid controls are dependent on the functionality within the XamGrid, but it may be marked as an internal class as a sort of "removal" from the toolset. I cannot say for certain what exactly will become of the XamGrid at this point in time.
It is worth noting that the plan to retire the XamGrid in favor of the XamDataGrid is not a new one, though. The message I provided in the post above has been on each and every one of the XamGrid documentation topics since 2016.