Skip to main content
Version: older

v3.6.2 to v3.7.0

AUTOMATIC MIGRATION​

  1. install node.js (16.16.0)

  2. Use the BIAToolKit to migrate the project

  3. Manage the conflict (2 solutions)

    1. In BIAToolKit click on "4 - merge Rejected" and search <<<<< in all files.
    • Resolve the conflict manually.
    1. Analyze the .rej file (search "diff a/" in VS code) that have been created in your project folder
    • Apply manually the change.

  4. Change source path and run the script V3.6.2_to_V3.7.0_Replacement.ps1

  5. Apply other manual step (describe bellow) at the end if all is ok, you can remove the .rej files (during the process they can be useful to resolve build problem)

MANUAL STEPS​

FRONT​

1. For screens that use views​

  1. In index.component.html, in bia-table-controller, add tableState param.

    <bia-table-controller
    ...
    [tableState]="tableState"
    ></bia-table-controller>

  2. In index.component.html, in bia-table, add sortFieldValue and stateSave params

    <bia-table
    ...
    [sortFieldValue]="sortFieldValue"
    (stateSave)="onStateSave($event)"
    ></bia-table>

  3. In index.component.ts, add the following member variables (above the constructor) and filled in the value of sortFieldValue

    tableState: string;
    sortFieldValue = 'the name of the column sorted by default';

2. Migration Angular 13​

  1. Migration Angular 13 : original command is

    ng update @angular/core@13 @angular/cli@13 --force ng update @angular-eslint/schematics@13 but it will be applied by the automatic migration so normally you do not have to apply it

    Just verify that '.gitignore' include '.angular/cache'.

  2. Migration PrimeNg 13 : The original command is ng update primeng@13 but it will be applied by the automatic migration so normally you do not have to apply it

    some prime ng icons name change:

    • pi-star-o => pi-star (will be automatically change in bia component)
    • pi-star => pi-star-fill (will be automatically change in bia component)
    • pi-circle-off => pi-circle
    • pi-circle-on => pi-circle-fill

    If you use it (except in bia template page = bia appear in path of the file) rename them.

4. Other​

  1. If you have a component that inherits from the bia-table-controller.component.html component, replace your html with that of the bia-table-controller.component.html component, then reapply your specific changes.

  2. PrimeNg component are disable by default.

    • If you use some primeNg component not used in BIADemo you should apply one of this correctif:
      • Uncomment the import and listing in const PRIMENG_MODULES of file
        \Angular\src\app\shared\bia-shared\bia-shared.module.ts
      • Import it in the module(s) where you need to use it (this solution make faster application for first load).

  3. Bia-table-config => bia-field-config

    1. Replace components/table/bia-table/bia-table-config by model/bia-field-config
    2. Replace BiaListConfig by BiaFieldsConfig
    3. Replace PrimeTableColumn by BiaFieldConfig

  4. In initTableConfiguration function of the CRUD index

    1. Add "isRequired: true" in BiaFieldConfig when field is required (information can be see in initForm() of your-feature-table/your-feature-table.component.ts with "Validators.required").
    2. Comment/remove the subscribe and the change of date format.
   private initTableConfiguration() {
=>    //this.sub.add(this.biaTranslationService.currentCultureDateFormat$.subscribe((dateFormat) => {
      this.tableConfiguration = {
        columns: [
          Object.assign(new BiaFieldConfig('msn', 'plane.msn'), {
=>           isRequired: true,
          }),
          Object.assign(new BiaFieldConfig('isActive', 'plane.isActive'), {
            isSearchable: false,
            isSortable: false,
            type: PropType.Boolean
          }),
          Object.assign(new BiaFieldConfig('lastFlightDate', 'plane.lastFlightDate'), {
            type: PropType.DateTime,
=>            //formatDate: dateFormat.dateTimeFormat
          }),
          Object.assign(new BiaFieldConfig('deliveryDate', 'plane.deliveryDate'), {
            type: PropType.Date,
=>            //formatDate: dateFormat.dateFormat
          }),
          Object.assign(new BiaFieldConfig('syncTime', 'plane.syncTime'), {
            type: PropType.TimeSecOnly,
=>            //formatDate: dateFormat.timeFormatSec
          }),
          Object.assign(new BiaFieldConfig('capacity', 'plane.capacity'), {
            type: PropType.Number,
            filterMode: PrimeNGFiltering.Equals,
=>            isRequired: true,
          }),
          Object.assign(new BiaFieldConfig('planeType', 'plane.planeType'), {
            type: PropType.OneToMany
          }),
          Object.assign(new BiaFieldConfig('connectingAirports', 'plane.connectingAirports'), {
            type: PropType.ManyToMany
          })
        ]
      };

      this.columns = this.tableConfiguration.columns.map((col) => <KeyValuePair>{ key: col.field, value: col.header });
      this.displayedColumns = [...this.columns];
=>    //}));
  }

BACK​

  1. Modified your DtoToRecord methods (use for CSV extract) of the Mapper classes in the Domain layer by following the example in the BIADemo project: TheBIADevCompany.BIADemo.Domain.PlaneModule.Aggregate.PlaneMapper

  2. Move all your WorkerService jobs in application layer :

    1. Cut all classes in ...WorkerService\Job
    2. Paste them in ...Application\Job
    3. modify the namespace => replace WorkerService.Job by Application.Job
    4. the class should be public (change it if there are private or internal).
    5. resolve using in ...WorkerService\Worker.cs

  3. Move the recurring jobs init in DeployDB

    1. Search RecurringJob.AddOrUpdate in ...WorkerService\Worker.cs

    2. Move this code after RecurringJob.AddOrUpdate<SynchronizeUserTask> of ...DeployDB\Program.cs

    3. Copy the "Tasks" settings from ...WorkerService\appsettings.json to ...DeployDB\appsettings.json

    4. In ...WorkerService\appsettings.json the "CRON" values can be remove ex:

         "Tasks": {
            "WakeUp": {
               "Url": "http://localhost/BIADemo/App|http://localhost/BIADemo/WebApi/api/Auth/frontEndVersion"
            },
         },

    5. In ...DeployDB\appsettings.json only the "CRON" values should be keep:

         "Tasks": {
            "WakeUp": {
               "CRON": "0 6-17 * * *"
            },
            "SynchronizeUser": {
               "CRON": "0 6 * * *"
            }
         },

BUILD​

  1. Due to .Net 6.0 you should change the build task to use Visual Studio 2022:
    • Add a Task "Visual Studio build (Side-by-side)" and set the same parameter than the "Build solution" Task.
    • Remove the old Task "Build solution"
  2. Adapt the copy path
    • In the 3 copy tasks replace net5.0 by net6.0
    • In the "Copy Files Worker service" change the Contents by ** and the Target Folder by $(build.artifactstagingdirectory)/$(CompanyName).$(ProjectName).WorkerService

DEPLOY​

  1. The service worker should be deploy as a windows service and not more as web Application:
    • In all environment, change the version of the task "Deploy Service as Web" used the V4 (BIA Deploy Service - V3.7.0 - *) and rename the task "Deploy Service"