New feature to let a Business Object persist Bag properties to be used via a relationship from other Business Objects
If an rule must inject Target Objects into the migration stream, these Target Objects must now be defined as injectable in Studio
Engine Framework
Modified to accommodate changes to Target Engine (below)
Code generation is now multi-threaded and considerably faster
Target Engine
New InterfaceItem and TargetItem properties for manual rules and bags.
New feature to recover bag properties containing advanced object graph via a relationship
Requires refactoring of Visual Studio Target Engine projects, see below
Data services extensions
When validating from Studio, the Data Services extensions supplied by hopp (Sql Server, Oracle and DB2) will not validate any connection string containing references to secrets or constants. This reduces validation time as the validation will no longer wait for a connection timeout
Portal
Director Client integration
Operations are now available inside the portal with all the functionalities from the existing Director Client Windows application
Each user has a dedicated page with the unexpected error logs with with the datetime of occurence in order to facilitate the process of bug or error reporting. The page is available in the Account section of the user:
Administrators have access to all users error logs page in Settings area:
Installation and Refactoring
Target Engine projects
Manual Rules and Bags in Target Engine projects accessing must be refactored if they
Access the BusinessEntity property or the SelectImportedBusinessEntity methods
Access the ImportedItem or RootImportedItem property
Use the generated TargetEntity wrappers to inject or modify Target Entities
Access relationships to recover Interface- or TargetXml
Rules and Bags in need of refactoring are easily identified as they will not compile after running the new code generation
Hopp tech may assist in this refactoring
TargetEngine- and SourceEngineGenerated csproj files
Upgrade from netstandard2.1 to net6.0
Upgrade Nuget package references
Microsoft.EntityFrameworkCore.SqlServer to version 6.0.16
System.Data.SqlClient to version 4.8.5
Database
Please back up all database before running refactor scripts
Run attached MigrationDb.10.sql in all Migration databases
Workstations
Reinstall Studio
Reinstall Engine Framework
Reinstall LIbraries
Reinstall Director client (minor fix in relation to local debug from Visual Studio)
Reinstall VsExtension (2019 or 2022 as required)
Reinstall DataServices Extensions (if installed)
Sql Server
Oracle
DB2
Even though the Director Client has been ported to the Portal, it should not be uninstalled. It is currently still used when deploying and debugging engines from Visual Studio
Master Server
Reinstall Director Runtime
Redeploy Portal and all extensions
Run attached Master.Db.03.sql in the Master database
Run attached ProjectDb.04.sql in all Project databases
Lars Kjaersgaard
Studio
Engine Framework
Target Engine
Data services extensions
Portal
Director Client integration
Error Log pages
Each user has a dedicated page with the unexpected error logs with with the datetime of occurence in order to facilitate the process of bug or error reporting. The page is available in the Account section of the user:
Administrators have access to all users error logs page in Settings area:
Installation and Refactoring
Reinstall Director Runtime
Redeploy Portal and all extensions
Run attached Master.Db.03.sql in the Master database