V6.0.* to V6.1.*

Prerequisites

BIA Framework Migration

Delete from your Angular projects all package-lock.json and node_modules folder

Use the BIAToolKit to migrate the project

info

Run it automatically by clicking on Migrate button
or
Execute each step manually until step 3 - Apply Diff

warning

Mind to check the output logs to check any errors or missing deleted files

Manage the conflicts

info

• SOLUTION 1 : Merging rejected files

  execute step 4 - Merge Rejected (already executed with automatic migration)
  resolve the files marked as conflicts in your favorite IDE or merge editor

• SOLUTION 2 : Analyzing rejected files - MANUAL MIGRATION ONLY

  analyze all the .rej files (search "diff a/" in VS code)
  apply manually the changes into your files

warning

You must keep your current Rights.cs file even if it is marked as deleted

⚡COMMIT

For each Angular project :

run npm install

run npm audit fix

⚡COMMIT

Download the migration script (.txt - Save link as), then :

change source path of the migration script to target your project root and your Angular project

run it for each of your Angular project (change the Angular source path each time)

⚡COMMIT

Download the rights to permission migration script (.txt - Save link as), then :

change source path of the migration script to target your back end project sources

run it

⚡COMMIT

Relaunch BIAToolKit and reload your project on Modify existing project tab, or click on Refresh project informations button if it still opened

Resolve missing and obsolete usings in back-end with BIAToolKit (step 6 - Resolve Usings)

Resolve building issues into Back

Resolve building issues into your Angular projects

tip

For manual management of conflitcs case : you can remove the .rej files

⚡COMMIT

For each Angular project, launch the npm run clean command

Clean back-end solution

⚡COMMIT

Offline Mode

If you use offline mode, it is now enabled by setting the enableOfflineMode parameter to true in the all-environments.ts file.