Forums Home / ComponentOne / WPF Edition
Posted by: rand.random on 2 December 2020, 12:10 am EST
rand.random
Posted 2 December 2020, 12:10 am EST
I have just read your blog about .NET 5
https://www.grapecity.com/blogs/componentone-is-dot-net-5-ready-learn-more-anout-dot-net-5-controls-support-and-more
and sadly for us C1DataGrid will be unsupported.
We are heavily using it and I would like to ask if there is a migration plan anywhere to be found?
And if there isn’t one already available could you please share the information need to make the migration as smooth as possible?
Ruchir.Agarwal
Posted 2 December 2020, 7:37 pm EST
Hello,
Yes, as you know C1DataGrid would not be supported in .NET 5, as it is now legacy.
Also, we don’t have any migration guide, there are too many use cases. However, to help you please refer following link for comparison between the two grids: https://www.grapecity.com/componentone/docs/wpf/online-datagrid/DataGridFeatureComparisonMatrix.html#
Regards,
greg.lutz
Posted 3 December 2020, 6:51 am EST
Hello,
We appreciate this feedback, and it will help us determine any changes to the roadmap we may need to make. We have made many advancements and commitments to FlexGrid as our #1 datagrid in all platforms, and moving forward even if we do port C1DataGrid to .NET 5 it will not be receiving any more updates or new features.
We are interested to know what features of C1DataGrid that you are using and we can help you replace it with FlexGrid?
It’s also worth noting that we will continue to support our .NET 4.5.2 controls in .NET 5 apps, so in the meantime, you can continue to use that version when you first migrate to .NET 5, and then replace the controls down the road when/if C1DataGrid is ported, or you find a way to replace it.
Regards,
Greg Lutz, Product Manager
rand.random
Posted 8 December 2020, 8:56 pm EST
Sorry, for my late response.
Thanks for the answers so far.
[quote]We are interested to know what features of C1DataGrid that you are using and we can help you replace it with FlexGrid?
[/quote]
We still don’t know, we are in a very early phase of evaluating if .NET 5 is possible or not, it will most likely take some time before we can have an in-depth look into this topic.
We were just surprised to see the announcment, since we are only using C1DataGrid, our project is 10 years old, so I actually can’t even tell you why we chose the C1DataGrid over the C1FlexGrid that long ago.
Though after reading the comparison Ruchir.Agarwal shared, I was surprised to read that C1FlexGrid supports “bound mode” I had thought that it only supports “unbound mode” did that change over time, or am I just remembering incorrectly?
[quote]It’s also worth noting that we will continue to support our .NET 4.5.2 controls in .NET 5 apps, so in the meantime, you can continue to use that version when you first migrate to .NET 5, and then replace the controls down the road when/if C1DataGrid is ported, or you find a way to replace it.
[/quote]
Can you elaborate what the disadvantages of using 4.5.2 controls in a .NET 5 project would be?
This would certainly help us with our decision, since C1DataGrid is heavily used in our project, and doing both the transition to .NET 5 and replacing C1DataGrid with C1FlexGrid will be hard to sell to my superiors.
greg.lutz
Posted 9 December 2020, 2:10 am EST
Thank you for the feedback.
Can you elaborate what the disadvantages of using 4.5.2 controls in a .NET 5 project would be?
With .NET 5, one of the key features was that you could package .NET with the application. The main disadvantage of using .NET 4.5.2 controls in a .NET 5 application is that the user must have .NET Framework installed as a prerequisite.
Also, using the .NET 4.5.2 controls, you won’t get any new features that depend on .NET 4.5.3+, such as high DPI (which was introduced in .NET 4.7 and now supported in our .NET 5 controls). High DPI is pretty much the only obvious feature we see regularly.
Regards,
Greg L
