Skip to content

Conversation

@TheCodeTraveler
Copy link
Collaborator

@TheCodeTraveler TheCodeTraveler commented Oct 7, 2025

Description of Change

This PR adds support for .NET 10

PR Checklist

  • Has tests (if omitted, state reason in description)
  • Has samples (if omitted, state reason in description)
  • Rebased on top of main at time of PR
  • Changes adhere to coding standard

Additional information

This PR will be merged when .NET 10 GAs in November 2025

Breaking Changes

  • .NET 10 Required
  • Removed Deprecated IPopup
  • Removed Deprecated MauiPopup
  • Removed Deprecated PopupHandler
  • Removed Deprecated PopupExtensions

@TheCodeTraveler TheCodeTraveler added the breaking change This label is used for PRs that include a breaking change label Oct 7, 2025
{
#if NET9_0
#if NET10_0
ReferenceAssemblies = Microsoft.CodeAnalysis.Testing.ReferenceAssemblies.Net.Net90;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we also update net10 here?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup! We're waiting on Microsoft to release support for testing Analyzers with .NET 10. Microsoft.CodeAnalysis.Testing.ReferenceAssemblys.Net.Net100 hasn't yet been released.

For now, the Analyzer tests all fail.

I assume (hope) Microsoft will push support for this before .NET 10 GAs.

{
#if NET9_0
#if NET10_0
ReferenceAssemblies = Microsoft.CodeAnalysis.Testing.ReferenceAssemblies.Net.Net90;
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reference assemblies net10?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup! We're waiting on Microsoft to release support for testing Analyzers with .NET 10. Microsoft.CodeAnalysis.Testing.ReferenceAssemblys.Net.Net100 hasn't yet been released.

For now, the Analyzer tests all fail.

I assume (hope) Microsoft will push support for this before .NET 10 GAs.

TheCodeTraveler and others added 18 commits October 9, 2025 14:54
This should no longer be necessary now that we don't have internal access to MAUI
- Added conditional compilation for .NET 10 in `CSharpAnalyzerVerifier`.
- Updated `XmlnsDefinition` attributes for .NET MAUI compatibility.
- Upgraded `Xamarin.AndroidX.Media3` packages to version 1.8.0.
- Added `using` directives for `Microsoft.Maui` namespaces across files.
- Adjusted platform-specific code to use updated APIs (e.g., `session.PlatformToken`).
- Included Android resource `textureview.xml` in the project.
@ne0rrmatrix
Copy link
Contributor

Looks like there is runtime issues still for Android and iOS/macOS. The issue is with FlyoutBackgroundColor and using AppThemeBinding to set light and dark in AppShell.xaml. The AppThemeBinding is not working with the new XAML SourceGen when you nest Bindings.

ATM I cannot run android or iOS without removing AppThemeBinding from AppShell.xaml

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

breaking change This label is used for PRs that include a breaking change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[NET10] Switch to public MAUI types for AvatarView

4 participants