Not Supported Constructs

The following LLBLGen Pro Designer constructs are not supported for Entity Framework Core v8. Using an element on this list will result in a validation error of the project.

• Stored Procedure Calls
• Multiple catalogs per project
• JSON mappings
• Triggers in SQL Server
• 'Entity Splitting' with an entity mapped onto multiple tables.

Model value types and Complex types

We generate model value types (so e.g. 'Address', not .net's int32 etc.) as 'Owned types' and not as the new feature for Entity Framework Core: 'Complex types'. The main reason is this open issue: https://github.com/dotnet/efcore/issues/31376 which implies that all complextypes have to be not null/required but the requirements for valuetypes for owned types as we have in previous versions are less strict: they can be null/optional.

Changing the way we generate model value types would break code for existing customers and also introduce problems they previously didn't have. If Microsoft implements less strict rules in the future we might introduce a choice for selecting which output type to use for model value types.