Supported Constructs

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

  • All supported constructs on Entity Framework v4
  • Enums (using .typeimports files, see the Designer documentation for details on this).
  • Table Valued Functions
  • Spatial types (SqlGeometry and SqlGeography) in SQL Server, database first scenarios. If you're not using Code first, the generated EDMX will use the default values for SRID for geometry (0) and geography (4326). Entity Framework v6 requires a reference to the EntityFramework.dll from nuget in the generated Model project if you use spatial types in your entity classes.
Info

When using many to many (m:n) relationships, the 'intermediate' entity is not generated if this entity has no non-pk fields. An intermediate entity with only pk fields means that the m:n relationship is a 'pure' m:n relationship. If the intermediate entity does have non-pk fields, the m:n relationship is seen as an 'objectified' relationship. Entity Framework doesn't support objectified m:n relationships and the m:n relationship and its navigators will then be ignored.

The supported databases are the same as for v1: (depending on the fact that the ADO.NET provider build supports EF v5 or v6)

For .NET Framework:

  • SQL Server 2000 and higher
  • MySql (DevArt provider)
  • PostgreSql
  • DB2
  • Firebird

For .NET Standard:

  • SQL Server 2000 and higher
  • PostgreSql
  • Firebird