LLBLGen Pro Support System General Chat feed

Migrating to EF core 10 with MySQL by Otis

Otis — Tue, 17 Feb 2026 08:15:45 GMT

We don't support EF Core on mysql. For a long time the provider needed from devart wasn't good enough so we didn't support it because of that. When they finally had a provider that worked we decided not to support them (devart) anymore. The main issue is that a commercial ADO.NET provider is needed from them. We kept mysql support for our own runtime for backwards compatibility.

Entity Framework 6 works on .net standard and thus on .net 10, but not sure how it works with blazor.

Migrating to EF core 10 with MySQL by JanRHansen

JanRHansen — Tue, 17 Feb 2026 06:30:34 GMT

The title is a bit misleading. It should have been "Migrating to EF core 10 with MySQL". Feel free to update if possible.

My current setup is - LLBLGen 5.13 handling a model for - my old ASP.NET webforms (framework 4.8 ) (yes, that old) - and a MySQL 8 database - using the LLBLGen Pro Runtime

My gold is to to update/migrate to a Blazor web solution on .NET 10, but this leaves me with a few questions.

I'm sort of stuck with the MySQL requirement, but according to https://dev.mysql.com/doc/connector-net/en/connector-net-entityframework-core.html, the MySQL Connector/NET v. 9.4 supports .NET 10 preview - and according to https://dev.mysql.com/doc/relnotes/connector-net/en/news-9-6-0.html a 9.6 version has been released in january 2026. I'm guessing/hoping that the .NET 10 support is "OK", but their documentation is not very updated.

Also, according to https://www.llblgen.com/Pages/EntityFramework.aspx - the supported Entity Framework Version is "Entity Framework (not on .NET Standard)". No mention of Entity Framework Core. Am I missing something?

Assuming that .NET 10 is supported (do you have nay knowledge about this?) what would be a good way to proceed?

Should I create a new llblgen project, or can I have both my current model and a new one in the same? I need to be able to continue releasing on the existing platform, and I foresee this will be a lengthy project Any suggested path? Also, if I want to try out the Entity framework Core v10 target framework, how is that best achieved?

Sorry if the questions are a bit inconcrete, I'm looking for guidance more than definite answers

UnitOfWorkBlockTypes by Otis

Otis — Sat, 05 Jul 2025 06:37:38 GMT

Yes, so you first set the FK field in Y to NULL, add it to the UOW, add X to the UOW and set the commit order in such a way that updates are run before deletes. If the FK in Y isn't nullable, you have to delete the Y instance, so add that first to the UOW, then X. You can also change the FK constraint in the database to support cascades, e.g. let the DB set the FK to null OR delete the Y instance

UnitOfWorkBlockTypes by User001

User001 — Fri, 04 Jul 2025 08:19:17 GMT

Let's say I have a Parent Table called X, Child Table called Y. They are link in terms of Primary Key and Foreign Key with a Field called F1.

Want to delete Parent Class but couldnt because I know that there is still a Child Table related to that Parent Table has not deleted.

Do I need to setup own UOW2.CommitOrder? Thanks.

Is LLBLGen ready for Npgsql 10? by Otis

Otis — Thu, 12 Jun 2025 15:08:19 GMT

mbp wrote:

Thanks for your reply.

Of course, we are also not happy if those sync methods stopped worked, primarily because we have code that is not using async calls, that would have to be rewritten.

You are right that Npgsql 10 should work (if they add a toggle to enable sync I/O), so it probably will be in Npgsql 11 that it could be a real problem.

In any case, if we ever come to a situation where we can't use the latest bits from Microsoft, and LLBLGen is preventing us to upgrade, then that would probably mean we would have to look for alternatives. So the goal with my post was merely to give me some kind of hope that we can use LLBLGen for many years forward, even if Microsoft does things we disagree with :-)

If the current npgsql does what you need, you don't need to upgrade to newer version that ditches existing api's. So I guess it's only for new code targeting .net 10+ that might be affected. Existing projects targeting .net 8 with e.g. npgsql 8/9 will keep on working just fine.

I don't want to give you false hope, as in the end it's not a problem we create, so there's little we can do but wait and see. But for the coming years (2 at least I think) I wouldn't worry about it

Is LLBLGen ready for Npgsql 10? by mbp

mbp — Thu, 12 Jun 2025 06:23:05 GMT

Thanks for your reply.

Of course, we are also not happy if those sync methods stopped worked, primarily because we have code that is not using async calls, that would have to be rewritten.

You are right that Npgsql 10 should work (if they add a toggle to enable sync I/O), so it probably will be in Npgsql 11 that it could be a real problem.

In any case, if we ever come to a situation where we can't use the latest bits from Microsoft, and LLBLGen is preventing us to upgrade, then that would probably mean we would have to look for alternatives. So the goal with my post was merely to give me some kind of hope that we can use LLBLGen for many years forward, even if Microsoft does things we disagree with :-)

Is LLBLGen ready for Npgsql 10? by Otis

Otis — Thu, 12 Jun 2025 06:11:10 GMT

I replied last year in their issue: https://github.com/npgsql/npgsql/issues/5865

We have an async api, so it should be fine in general, IF you only call async methods. However we don't implement CommitAsync calls as that's not in .netstandard2.0. We ship an older npgsql for the driver so it's only at runtime.

My personal opinion is that this is a stupid move of them. Removing APIs that are used by many is beyond pointless. You can deprecate things and signal to the user 'hey it's better to use the alternative' but there's little else to it.

But in the end it's all what-if, they haven't released v10 yet and in v10 it still should work ok. We'll see.

Is LLBLGen ready for Npgsql 10? by mbp

mbp — Wed, 11 Jun 2025 07:59:36 GMT

Hi,

I read on Npgsql 9.0 release notes, that they are considering dropping support for synchronous APIs. Link: https://www.npgsql.org/doc/release-notes/9.0.html

I want to ask if LLBLGen will be ready to work without those APIs, when Npgsql 10 comes out?

.Net Upgrade to 4.8 by Otis

Otis — Thu, 06 Feb 2025 20:31:32 GMT

Jayr1985 wrote:

We need to move a legacy application that uses LGP files from.Net 2.0 to.Net 4.8. Please provide instructions on how to update the.lgp file to the most recent version and regenerate the class objects since we don't have the older version of Designer installed. Additionally, the project upgraded to.net 4.8 without any build issues when we used class objects generated from.lgp. Please provide guidance on the next steps. We have also purchased the most recent pro license.

Also answered via email:

To migrate the project, please see: https://www.llblgen.com/Documentation/5.11/Designer/Migratingv2xProject.htm To migrate your code, please see: https://www.llblgen.com/Documentation/5.11/LLBLGen%20Pro%20RTF/migratingcode.htm

Most breaking changes are likely not something you'll run into, but just in case, all breaking changes are documented there.

.Net Upgrade to 4.8 by Jayr1985

Jayr1985 — Thu, 06 Feb 2025 13:24:33 GMT

We need to move a legacy application that uses LGP files from.Net 2.0 to.Net 4.8. Please provide instructions on how to update the.lgp file to the most recent version and regenerate the class objects since we don't have the older version of Designer installed. Additionally, the project upgraded to.net 4.8 without any build issues when we used class objects generated from.lgp. Please provide guidance on the next steps. We have also purchased the most recent pro license.