What's new in Entity Framework support in LLBLGen Pro v5.9

This section describes all changes, new additions, breaking changes and fixes made to the Entity Framework support.

The following new features / changes have been made to the support for Entity Framework / Entity Framework Core.

Entity Framework Core 6 support. You can now select Entity Framework Core 6 as your target framework in the LLBLGen Pro designer. More information
Nullable reference type support for Entity Framework Core 5 and 6.
Firebird projects now generate code targeting the v8.0.0 provider for Entity Framework Core 5

What's new in Entity Framework support in LLBLGen Pro v5.8

The following new features / changes have been made to the support for Entity Framework / Entity Framework Core.

Entity Framework Core 5 support. You can now select Entity Framework Core 5 as your target framework in the LLBLGen Pro designer. More information
Oracle is now a supported database for Entity Framework Core v3.x+
Firebird projects now generate code targeting the v7.10.1 provider.
Entity Framework Core: fields in entities are now generated in the class in the order they're specified in the entity type: if no field ordering is specified, they'll be generated alphabetically, like before. If there's a fieldorder specified, they'll be generated in that order.

The following new features / changes have been made to the support for Entity Framework / Entity Framework Core.

Entity Framework Core 3.x is now also supported on .NET Standard 2.0.
Entity Framework Core 3.x now references the latest EF Core 3.1 version in new generated projects.
Entity Framework Core 2.2 has been marked 'legacy' as it's out of support by Microsoft.

The following new features / changes have been made to the support for Entity Framework / Entity Framework Core.

Entity Framework Core 3 support. You can now select Entity Framework Core 3 as your target framework in the LLBLGen Pro designer. More information
Entity Framework v6 for .net standard 2.1 support. You can now select .NET Standard 2.1 as target platform for Entity Framework 6. More information
.NET Standard 2.1 support for Entity Framework v2.2. You can now select .NET Standard 2.1 as target platform for Entity Framework Core v2.2.

The following new features / changes have been made to the support for Entity Framework / Entity Framework Core.

Entity Framework Core v2.2 support. EF Core 2.2 is supported on .NET 4.6.1 or higher and .NET Standard 2.0. Please see the Entity Framework Core 2.2 specific documentation about what's supported in this release on EF Core 2.2 and how it's used. Supported databases: SQL Server, PostgresSQL and Firebird
Entity Framework Core v2.0 is now marked as legacy. Users should move to at least v2.1 as v2.0 doesn't have LTS support from Microsoft.

The following new features / changes have been made to the support for Entity Framework / Entity Framework Core.

Entity Framework Core v2.1 support. EF Core 2.1 is supported on .NET 4.6.1 or higher and .NET Standard 2.0. Please see the Entity Framework Core 2.1 specific documentation about what's supported in this release on EF Core 2.1 and how it's used. Supported databases: SQL Server, PostgresSQL and Firebird

Firebird is now a supported database for Entity Framework Core 2.0 / 2.1
Entity Framework 6 is now marked 'legacy' so for new projects it's shown below the list of major frameworks.
Entity Framework Core v1, v2 and v2.1 now have a partial method, OnModelCreatingComplete, which is called at the end of the generated OnModelCreating method, to append work to that method without the necessity of inheritance.

As v5.4.0 is released prior to Entity Framework Core 2.1, the new features coming with EF Core 2.1 will be added as soon as EF Core 2.1 is RTM.

The following new features / changes have been made to the support for Entity Framework / Entity Framework Core.

The generated POCO classes for CodeFirst / DbContext as well as for EF Core 1 and 2 now have a partial method OnCreated() which is called at the end of the ctor. This can e.g. be used for custom types for navigators to be created automatically, e.g. when a specific sorted list is needed for a specific navigator.

The following new features / changes have been made to the support for Entity Framework Core

Entity Framework Core v2.0 support. EF Core 2.0 is supported on .NET 4.6.1 or higher and .NET Standard 2.0. Please see the Entity Framework Core 2.0 specific documentation about what's supported in this release on EF Core 2.0 and how it's used.
.NET Standard 2.0 support (for EF Core 2.0).
Entity Framework Core 1.0 is now marked 'legacy' in the designer. New projects should use Entity Framework Core v2.0.

The following new features / changes have been made to the support for Entity Framework Core

Netstandard 1.6 support. When selected as target platform, the designer will generate a csproj file in the Visual Studio 2017 format, targeting Netstandard 1.6.
Setting to generate a field as a readonly property and a setting to generate readonly fields as readonly properties. Both use the Entity Framework Core 1.1.x feature of backing fields instead of auto-properties.
Support for Read-only entities
Setting to select the CollectionType for a navigator which returns a set. It's now possible to specify as type IEnumerable<T> and ICollection<T> instead of the default List<T>.
Setting the CollectionType for a navigator to ICollection<T> and List<T> will now produce code in the constructor of the entity to set the navigator to an instance of HashSet<T> and List<T> respectively. If you select IEnumerable<T> as navigator return type, you have to instantiate the navigator manually.

Entity Framework Core v1.x support. Entity Framework Core v1.x is now fully supported.

No additions have been made for Entity Framework support in v5.0.

Entity Framework 6: Code First support. Code first is now fully supported for Entity Framework v6.
Entity Framework 6: Unintended Code First triggering interception support added For normal DbContext usage the OnModelCreating method is also overriden in DbContext, and will throw an exception, as it will only be invoked if the user has specified the connection string wrong, which will cause EF to go into CodeFirst mode.

Entity Framework 6 support. Entity Framework v6 is now fully supported.
New settings for Spatial types and StoreGeneratedPattern control. These settings are available on Entity Framework v5 and up.