The LLBLGen Pro Blog: LLBLGen Pro v5.5.5 and v5.6.1 have been released!

We've released the RTM versions of LLBLGen Pro v5.5.5 and LLBLGen Pro v5.6.1! See below what's new / fixed in these releases.

New features

v5.6.1: Net standard 2.1, Entity Framework Core v3, EF 6 on Net standard support

Additionally to the fixes below, we've added support for the following new features in v5.6.1

.Net standard 2.1 support (Designer, LLBLGen Pro Runtime Framework, EF Core, EF, derived models)
Entity Framework v6.x on .Net standard support
Entity Framework Core 3.0 support. Additionally to this, we added Table-valued function support to Entity Framework Core 3.0 using FromSql() queries. Example:

using(var ctx = new MyGeneratedDbContext(connectionString))
{
    // pass 10 as the parameter value of the function.
    var results = ctx.UfnGetContactInformation(10).ToList();
    // do something with results
}

See for details What's new in Entity Framework support in LLBLGen Pro v5.6.1

Fixes

The following bugs have been addressed

LLBLGen Pro v5.5.5

(Database Drivers) - SQL Server time fields for temporal tables aren't seen as computable fields by the sqldriver
(Database Drivers, Designer Core, Designer UI) - It's possible to select tables when syncing with the database for a mixed sync source, which leads to an internal exception
(Designer Core) - Entity Framework 6, validation: not having a field mapped onto a computed column works in CodeFirst, not in DbContext, however the validator always assumes an error
(Designer Core) - If a group is renamed in the project explorer, the TVF elements in that group are kept in a group with the old name
(Runtime Libraries) - Linq: A .First() projection in a projection loses the type converters on the projected element
(Runtime Libraries) - Linq: a constant in the projection is embed in the compiled projection lambda, resulting in wrong resultsets with unioned queries
(Runtime Libraries) - Selfservicing: a projection with solely function calls in a union query could lead to a query without a from clause.

LLBLGen Pro v5.6.1

(Database Drivers) - SQL Server time fields for temporal tables aren't seen as computable fields by the sqldriver
(Database Drivers, Designer Core, Designer UI) - It's possible to select tables when syncing with the database for a mixed sync source, which leads to an internal exception
(Designer Core) - Entity Framework 6, validation: not having a field mapped onto a computed column works in CodeFirst, not in DbContext, however the validator always assumes an error
(Designer Core) - If a group is renamed in the project explorer, the TVF elements in that group are kept in a group with the old name
(Designer Core) - If there are multiple license files found the designer should pick the last one
(Designer UI) - Deleting the last element in a set in the project explorer could lead to an index out of range exception in the DevExpress treelist control
(Runtime Libraries) - Linq: A .First() projection in a projection loses the type converters on the projected element
(Runtime Libraries) - Linq: a constant in the projection is embed in the compiled projection lambda, resulting in wrong resultsets with unioned queries
(Runtime Libraries) - Remove dependency on SqlClient in ORMSupportClasses
(Runtime Libraries) - Selfservicing: a projection with solely function calls in a union query could lead to a query without a from clause.

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.