Guidelines for v2.x users
LLBLGen Pro v5 comes with a completely new designer, which works a little different from the previous versions. To help you get started with the new designer when you're used to the v2.x designer, please see the small list below.
- v2.6: 'Field mapped onto relation'.
- v2.6: 'Relation'.
- v2.6: 'Mark relation as hidden'.
v5.x: Not available. Simply remove the relationship
- v2.6: 'Mark field mapped onto relation as hidden'.
v5.x: Remove the navigator or set it to an empty string.
v2.6: Create project would also obtain relational model data.
v5.x: Create project creates empty project. You have to add relational model data manually afterwards. This is because model first doesn't require relational model data being read from the database. Relational model data from the database can be obtained manually using the project menu (or context menu on 'Relational Model Data ' in Project Explorer or Catalog Explorer) and choosing 'Add Relational Model Data from a Database'.
v2.6: 'Add entities mapped onto table/view' in Project
v5.x: Entities can be reverse engineered using the Catalog Explorer (Right click on the database node (e.g. SQL Server (SqlClient)), catalog, table, tables etc. Entity creation (model first) can be done also using cntrl-shift-E, through the project menu, through the toolbar, through Quick Model, or by right-clicking 'Entities'
v2.6: Automatically setting the IsIdentity field for SQL Server
v5.x: Reverse engineering: this is done automatically. Model first: set the sequence property of a field mapping in the 'Field mappings' tab on an entity editor to any of the sequences available, for SQL Server is this for example
SCOPE\_IDENTITY(). This can be automated with a Project Setting.
v2.6: 'Refresh catalog'.
v5.x: 'Sync Relational Model Data'. This is available in the context menus in Project Explorer and Catalog Explorer, through the Project menu or through the toolbar. See Sync Relational Model Data tab for details.
v2.6: Single database type per project.
v5.x: Multiple database types per project (e.g. 1 model, mapped onto Oracle and SQL Server schemas at the same time)
v2.6: Catalog Explorer not that
v5.x: Catalog Explorer very important, real part of the designer
v2.6: No validation.
v5.x: True deep validation and model synchronization.
v2.6: DDL SQL generated through additional templates.
v5.x: Database schema creation is integrated in the designer. It's activated through menu options ('Generate Database Create Schema script/ Update Schema script') in the context menu on Relational model data in Project Explorer and Catalog Explorer, or in the project menu.
v2.6: Sub-types could have their own identifying fields.
v5.x: Sub-types always inherit their identifying fields from their super-type
v2.6: Entities could be defined without at least one identifying
v5.x: Entities always have to have at least one identifying field set, unless it's mapped onto a view.