v3.1: New metadata builder API
Published by Marco on
The summary below describes major new features, items of note and breaking changes. The full list of issues is also available for those with access to the Encodo issue tracker.
This release is a “bridge” release that has the entire new Metadata API as well as the older version, which is marked as obsolete. It is intended that projects upgrade to this version only temporarily in order to more easily migrate to the 4.0 Metadata API. At that point, projects should immediately upgrade to Quino 4.0, from which all obsolete methods have been removed. Once 4.0 is available, there will be no more bug-fix releases for this release.
- Remove MetaId/Guid parameters from all metadata-building APIs
- Remove all dependencies and requirement for the
- Drastically reduce the surface of the
MetadataBuilderand base classes and improve dependency-resolution
AddForeignKeys()step to builders and
- Moved a lot of the builder-related extension methods from
- Added API to make it easier to add paths:
- Fixed generation of extension classes (e.g.
Data & Schema
- Made all
GenericObjectconstructors without an
- Removed last reference to the
GlobalContextfrom the data driver
- Improved flexibility of caching subsystem and added default global/immutable-data cache (in addition to the session-based cache).
- Fixed schema-migration for SQL Server: not-null constraints are now properly added and trigger-migration works with pure SQL statements and has been drastically simplified.
BootstrapServicesto the application to clearly delineate which objects are needed during the boostrap phase of configuration and startup
- Re-added all satellite assemblies for all Quino Nuget packages (ch-DE translations)
- Replaced all usages of DevExpress
- Added a lot of WPF controls and application implementation with a Sandbox.WPF project
PersistentEventHandlerAspecthas been renamed to
The next step is to bring out the 4.0 release, which will include the following features,
- Remove all currently obsolete code
- Reshape the metadata API to be more task-based and to significantly reduce the surface revealed to the application developer. This includes a drastic reduction of extension methods in
- Finish implementation and support for layouts everywhere (specifically as they are used for titles).
Quino.Datato reduce the surface exposed to application developers.
IPersistableand replace with a more appropriate and slimmer API.