Dotnet 10 changes

[Naseeha-SF4995]

Feature description

Upgrade and ensure compatibility with .NET 10.

Task Link : https://dev.azure.com/EssentialStudio/Mobile%20and%20Desktop/_workitems/edit/989018/

Purpose/benefits of the feature

•   Long-Term Support (LTS):
  

•   Performance Improvements
  

Use cases

• Improved .NET MAUI support for Android, iOS, Windows, and Mac Catalyst.

What problem it solves?

Do competitors have this this feature? If possible, add comparison and also share relevant links. Anyhow, this should be available in requirements doc which you can link

Analysis and design

Solution description

changed the obsolete value's to its corresponding new value in dotnet 10

Output screenshots

Post the output screenshots if an UI is affected or added due to this feature.

Areas affected and ensured

API Changes

Added:

• string ListView.GroupName { get; set; } //Bindable Property
• int ListView.GroupId { get; set; } // Bindable Property
• void ListView.Clear ();

Changed:

• object ListView.SelectedItem => Cell ListView.SelectedItem

Behavioral Changes

Describe any non-bug related behavioral changes that may change how users app behaves when upgrading to this version of the codebase.

Unit Test cases

Provide the unit testing written file details to understand the use cases considered in this implementation.

New Test cases

List out the test cases. Add details of how many new test cases were added for this bug. Attach links of PR for test bed sample changes and new test cases

Is automated against existing test cases and ensured zero breaking

Add a Centralized automation link

Testbed sample location

Provide the test bed sample location where code reviewers can review the new feature’s behaviors. This depends on the CI process that your team follows. It can be from NPMCI, HockeyApp, staging site, local server, etc.

Does it have any known issues?

If this feature contains any known issues, provide the proper details about the issues.

Release Notes contents

Provide release notes contents for this feature. References: https://help.syncfusion.com/maui/release-notes/

✅ Developer Checklist

• 1. Have you ensured the implementation works in iOS, Android, WinUI, and macOS (if supported)?
• 2. Have you ensured that all the public API changes (including changes in the interfaces) are approved from PLO through API review tasks?
• 3. Have you ensured there is no existing behavior change of other features due to this code change?
• 4. Have you updated the nuspec files if there are any dependency changes?
• 5. Have you created the build integration and extension tasks if there are any dependency changes?
• 6. Have you included the new dependency in the sample browser and AI samples?
• 7. Have you recorded the dependency changes in the release notes?
• 8. Have you enabled the necessary settings in your project, if you have created a new project?
• 9. Have you ensured no warnings or binding errors are suppressed?
• 10. Have you added a sample in the testbed for your feature?
• 11. Have you recorded this case in the unit test or UI test?
• 12. Have you ensured the new APIs and their comments are added as per standard?
• 13. Have you ensured the code does not expose or rely on internal framework APIs?
• 14. Have you included the license for your control (if it is stable)?
• 15. Have you ensured the cases mentioned in this link?
• 16. Have you tested the memory leak with your feature?
• 17. Have you ensured performance optimizations as per this guide?
• 18. If localization is needed, have you ensured the cases mentioned in this link?
• 19. Have you ensured the design follows the design system guidelines and supports both light and dark themes?
• 20. Have you ensured the new control/feature meets accessibility requirements?
• 21. Have you ensured RTL support?
• 22. If interaction-related code was added, have you used touch and gesture APIs from the core project?
• 23. Have you obtained approval before using any third-party packages?
• 24. Have you ensured testing is done in .NET 6.0, .NET 7.0, and .NET 8.0?
• 25. Have you ensured all points in the code review checklist?
• 26. Have you ensured all points in the common scenarios checklist are addressed at the implementation level and after feedback?
• 27. Have you run the sample browser and ensured your changes do not affect any existing functionality?
• 28. Have you ensured the same scenario works in Single Page View mode?