We've released the RTM versions of LLBLGen Pro v5.5.7 and LLBLGen Pro v5.6.3! See below what's fixed in these releases.

Fixes

The following issues have been addressed

LLBLGen Pro v5.5.7

• (Code Generator) - In model first, after creating a model in a new project, after sync, you immediately export the DDL SQL, the create statements aren't present in the generated script
• (Designer Core) - When two or more devs add fields to the same entity using model first, duplicate ordinals can occur after merge conflicts. The designer doesn't correct these.
• (Documentation) - Lazy Loading docs contain inconsistencies wrt LazyLoadingWithoutResultReturnsNew
• (Runtime Libraries) - A race condition in an edge case could lead to a NRE in the lambda cache in QuerySpec
• (Runtime Libraries) - Oracle: When an alias for a field exceeds 30 characters, the hashcode might result in a negative int which could lead to a '-' character in the alias name and if surrounding quotes were disabled it would lead to an invalid alias identifier
• (Runtime Libraries) - QuerySpec: The key construction for an expression tree would take enclosed objects into account which could lead to cache trashing
• (Runtime Libraries) - When a stored procedure resultset, with a datatable based typedview mapped onto it, receives new fields and the project isn't synced/regenerated again, it could be the projection of the new resultset to the typedview fails

LLBLGen Pro v5.6.3

• (Code Generator) - In model first, after creating a model in a new project, after sync, you immediately export the DDL SQL, the create statements aren't present in the generated script
• (Designer Core) - When two or more devs add fields to the same entity using model first, duplicate ordinals can occur after merge conflicts. The designer doesn't correct these.
• (Documentation) - Lazy Loading docs contain inconsistencies wrt LazyLoadingWithoutResultReturnsNew
• (Runtime Libraries) - A race condition in an edge case could lead to a NRE in the lambda cache in QuerySpec
• (Runtime Libraries) - Oracle: When an alias for a field exceeds 30 characters, the hashcode might result in a negative int which could lead to a '-' character in the alias name and if surrounding quotes were disabled it would lead to an invalid alias identifier
• (Runtime Libraries) - QuerySpec: The key construction for an expression tree would take enclosed objects into account which could lead to cache trashing
• (Runtime Libraries) - When a stored procedure resultset, with a datatable based typedview mapped onto it, receives new fields and the project isn't synced/regenerated again, it could be the projection of the new resultset to the typedview fails
• (Templates) - EFCore: Decimal types can lead to problems with precision/scale mismatches in model builder code

How to obtain the new bits?

You'll find the new RTM releases in the downloads section below 'My Account'. Of course the RTM builds of the runtimes are also available through NuGet.