.NET 10 Compatibility

[Orgbrat]

Since you use the CommunityToolkit.Maui Popup in your library and they have created a newer version for .NET 10, when will you upgrade your library to be .NET 10 Compatible?

[sebarslan]

Hi @Orgbrat,
I tested the application with .NET 10 in the main project and it worked correctly on my side. Could you please try it on your end as well?
If it doesn't work for you, I will add explicit .NET 10 support.

Thank you in advance, and wishing you a productive day.

[sebarslan]

Hello,
I had previously tested this without upgrading the Maui.Controls and CommunityToolkit.Maui versions. I will run the tests again after updating these packages, and if it still doesn’t work, I will add full .NET 10 support.

Thank you again, and have a great day.

[sebarslan]

Hello @Orgbrat ,
I’ve added .NET 10 support. If possible, could you please test it before I create the NuGet package?
Thank you very much, and have a great weekend.

[Orgbrat]

I have NullableDateTimePicker forked so that I may try it. But it will not build with latest Microsoft and CommunityToolkit.Maui bits.
It gets the following error which I am attributing to CommunityToolkit.Maui using Microsoft.Maui.Controls >= 10.0.10 and NullableDateTimePicker using 10.0.0. Below is the error I am receiving:

Warning As Error: Detected package downgrade: Microsoft.Maui.Controls from 10.0.10 to 10.0.0. Reference the package directly from the project to select a different version.
Sebarslan.Maui.NullableDateTimePicker -> CommunityToolkit.Maui 13.0.0 -> Microsoft.Maui.Controls (>= 10.0.10)
Sebarslan.Maui.NullableDateTimePicker -> Microsoft.Maui.Controls (>= 10.0.0)

I wanted to run this by you before I tried to fix this in my forked code. Was also unsure if it was related to the MauiVersion property not being set Explicitly in the project file to match the CommunityToolkit.Maui project

Orgbrat

[sebarslan]

Hello,
first of all, thank you very much for the tests.

It seems that CommunityToolkit 13.0.0 requires Maui.Controls 10.0.10 (which corresponds to $(MauiVersion)), but this workload is not available in Visual Studio yet.
So in the example project, we either need to set Maui.Controls 10.0.10 manually, or downgrade CommunityToolkit to 12.3.0.
Downgrading the CommunityToolkit version seems to be the more reasonable option. I will adjust that and commit again.

Could you please test it once more afterwards?
Wishing you a wonderful day.

[Orgbrat]

So I am using Visual Studio 2026 stable with the latest bits and it includes the stable .NET 10 SDK. The Maui.Controls are a separate nuget and I think if we are migrating to .NET 10 release then we should be using CommunityToolkit.Maui 13.0.0 with Maui.Controls 10.0.10. CommunityToolkit 12.3.0 uses .NET 10 Preview so how does that help the project move to .NET 10? Does the project not have to match what CommunityToolkit is using? Just asking questions...

[sebarslan]

Although CommunityToolkit 12.3.0 works with Maui 10.0.0, as you mentioned, using version 13.0.0 will indeed be the better option.
Until $(MauiVersion) returns 10.0.10 or higher, we can enter it manually and build the project that way.

I will prepare and publish the NuGet package with version 13.0.0 as soon as possible.
Thank you, kind regards.