.Net 11 support

[renemadsen]

This issus is to track progress for implementing support for .net 11

[bkoelman]

Is there already an AzDo or MyGet feed with dev packages compatible with EF Core 11?

[renemadsen]

@bkoelman since I do not use either of those I have no clue of those.

But if you can make a PR with github actions to push builds to those, I'll happily merge that in, but I'm not going to do a lot about it my self.

[bkoelman]

It requires account creation, secrets management, etc. As NuGet.org is already condigured, would you consider pushing preview packages there that support EF Core 11, such as here?

[renemadsen]

It requires account creation, secrets management, etc. As NuGet.org is already condigured, would you consider pushing preview packages there that support EF Core 11, such as here?

@bkoelman that I can do and we will get right into it, so we get a version 11 preview as soon as possible. .Net 11 release date is coming up soon anyways.

[vaital3000]

Hi @renemadsen,

Thanks a lot for maintaining this fork and keeping it up to date with new EF Core releases!

I'm reaching out on behalf of Dodo Engineering, the tech team behind Dodo Pizza. Many of our production .NET services run on MySQL through this provider, and we plan to move to .NET 11 shortly after GA, so the 11.0 release matters a lot to us.

Rather than just waiting, we'd like to help. Our team is ready to put engineering time into the project on an ongoing basis, with .NET 11 being the most pressing part for us:

• .NET 11 / EF Core 11: help finish the work on the net11 branch. The latest Build there (after Target .NET 11 and EF Core 11 preview for an 11.0.0-preview.1 release #440) has one failing job, Functional Tests on MariaDB 10.6.20 / Windows. We'd be happy to dig into that and anything else blocking 11.0.0-preview.1.
• Preview testing: run preview/RC packages against our services and report issues with minimal repros.
• Ongoing maintenance: bug fixes, reproducing and triaging issues, keeping tests and CI in shape.

We want this to save you time, not add to your workload, so a few questions:

1. Which areas would you most like help with right now?
2. Which branch should .NET 11 PRs target (net11 or master), and how would you like us to pick up issues so we don't overlap with work already in progress (including the Copilot PRs)?
3. Do you have a rough timeline for the 11.0 previews and the final release?

If a short call would make it easier to align, we're happy to set one up.

Thanks again for all your work!

[renemadsen]

Hi @renemadsen,

Thanks a lot for maintaining this fork and keeping it up to date with new EF Core releases!

I'm reaching out on behalf of Dodo Engineering, the tech team behind Dodo Pizza. Many of our production .NET services run on MySQL through this provider, and we plan to move to .NET 11 shortly after GA, so the 11.0 release matters a lot to us.

Rather than just waiting, we'd like to help. Our team is ready to put engineering time into the project on an ongoing basis, with .NET 11 being the most pressing part for us:

• .NET 11 / EF Core 11: help finish the work on the net11 branch. The latest Build there (after Target .NET 11 and EF Core 11 preview for an 11.0.0-preview.1 release #440) has one failing job, Functional Tests on MariaDB 10.6.20 / Windows. We'd be happy to dig into that and anything else blocking 11.0.0-preview.1.
• Preview testing: run preview/RC packages against our services and report issues with minimal repros.
• Ongoing maintenance: bug fixes, reproducing and triaging issues, keeping tests and CI in shape.

We want this to save you time, not add to your workload, so a few questions:

1. Which areas would you most like help with right now?
2. Which branch should .NET 11 PRs target (net11 or master), and how would you like us to pick up issues so we don't overlap with work already in progress (including the Copilot PRs)?
3. Do you have a rough timeline for the 11.0 previews and the final release?

If a short call would make it easier to align, we're happy to set one up.

Thanks again for all your work!

@vaital3000

1. Testing the preview in as many situations as possible would be the beste way to root out bugs.
2. Any fixes should go against the net11 branch, the master will be merged into net11 after the v11.0.0-preview.1 have been released, since it have received some fixes after I started the net11 changes. Then when net11 have been release we will merge back into master..
3. The v11.0.0-preview.1 will hopefully be out today.