LLBLGen Pro Support System General Chat feed

Linux CLI by Otis

Otis — Fri, 04 Sep 2026 07:14:17 GMT

hostileant wrote:

Oh that's great news, it's really only the Sync and Generate we need CLI for which is covered here.

If we're doing anything of substance it's done in the designer which we use on Windows anyway.

Cheers Ant

the cli tools are front ends for the rest of the core, which are still .net framework assemblies So it's not going to work to run these on linux I'm afraid

Linux CLI by hostileant

hostileant — Thu, 03 Sep 2026 06:28:24 GMT

Oh that's great news, it's really only the Sync and Generate we need CLI for which is covered here.

If we're doing anything of substance it's done in the designer which we use on Windows anyway.

Cheers

Ant

Linux CLI by Otis

Otis — Thu, 03 Sep 2026 06:20:13 GMT

hostileant wrote:

No problems, thanks for your time.

The cli tool is open source (and you can thus recompile it on .net 8+) but the main issue is the rest (the core assemblies of the designer). They have to be ported to .net 8+ and that turned out to be a bigger project than we wanted, so we stopped. It's not the C#/API but more the design with e.g. multiple app domains that caused issues. Hence we stayed on .net framework for the designer (and thus for the cli tooling)

Linux CLI by hostileant

hostileant — Thu, 03 Sep 2026 05:46:00 GMT

No problems, thanks for your time.

Linux CLI by Otis

Otis — Thu, 03 Sep 2026 05:44:02 GMT

No, sorry, we won't add a linux CLI

Linux CLI by hostileant

hostileant — Wed, 02 Sep 2026 23:18:39 GMT

Hey Team,

Any chance of a linux CLI for both agentic work and CI/CD pipelines?

We do currently manage it with wine installed on a linux box, and agents are proving very reliably able to edit the llblgen file directly before running a sync/regen.

Cheers

Ant

How to map column to jsonb in Entity Framework? by Otis

Otis — Fri, 21 Aug 2026 06:48:03 GMT

The templates don't have an extension point for this, so you have a couple of options:

alter the existing template (which leads to maintenance problems along the way), in the modelbuilder.lpt file, in the function DeterminePropertyAppendCalls all calls to append are determined. You can add a clause for jsonb there, like we did for decimal
use a custom template to emit a derived class for the modelbuilder which overrides the Mapentity method to append the property to the field.
manually add the override method in a derived class if it's just a couple of fields

We didn't know it requires that. I can add the method to v5.12/13 if you want (to the modelbuilder.lpt template). As it currently doesn't work as you said, it doesn't break code (as that would break anyway). That will be next week tho

How to map column to jsonb in Entity Framework? by mbp

mbp — Wed, 19 Aug 2026 09:25:15 GMT

We are generating Entity Framework code.

One of our columns is jsonb, and it must be mapped as such in Entity Framework, or queries will fail.

Generated code by default looks like this:

config.Property(t => t.Foo).HasColumnName("foo");

We manually have to do this change to make queries work:

config.Property(t => t.Foo).HasColumnName("foo").HasColumnType("jsonb");

I can see in LLBLGen Pro Designer, that LLBLGen does already know the DB type is jsonb, but how can we ensure "HasColumnType" is written in the Builder.cs file?

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