You can convert the version of a Nexacro Platform project from 14 to 17 by using the migration feature of Nexacro Studio.

Nexacro Studio provides the Migration Wizard, which automatically adjusts the configuration of a project such as structure, files and syntax. Moreover, the Studio offers several other tools for comparing and analyzing two different versions so that you can succeed in migration.

In this chapter, you will learn how to use the migration feature provided by Nexacro Studio.

Procedures

The process of migration through Nexacro Studio can be largely divided into four steps: opening a project, Migration Wizard, fixing errors and ending the migration.

• Opening a project is the beginning stage where Nexacro Studio reads your project and determines whether the project needs migration. If the project has been migrated before, you will be prompted to choose a mode for opening the project.

• The Migration Wizard is a migrator that automatically converts the version of your project from 14 to 17.

• Fixing errors refers to the finishing works where you check the errors resulting from the operation of the Migration Wizard and then fix those problems.

• Ending migration is the last stage where you decide not to open your project in the migration mode anymore after concluding that all the tasks related to the migration have been done.

Opening Project

In this step, Nexacro Studio opens your project that is based on Nexacro Platform 14. Afterwards, two possible scenarios will be played out depending on whether you have conducted the migration process for the project before: one scenario is about when you have never performed the migration process before while the other is about the opposite.

When you performs migration for the first time

When Nexacro Studio opens an unmigrated project, you will be asked whether you will conduct migration process as presented in the below picture.

If you want to conduct the process, click Yes.

When you have performed migration before

When you open a Nexacro Platform 14-based project that has been migrated before, Nexacro Studio will inform you that there is already a migrated version. Then, the Studio will ask you which action you will take next, as presented in the below picture.

Migration Wizard

When you first open a project that is based on Nexacro Platform 14, you will be asked whether to migrate the project. If you click "Yes", the Migration Wizard will begin running. The wizard is a tool that performs tasks that you otherwise have to do by yourself: to automatically establish the configuration of a project in a way that fits Nexacro Platform 17. For instance, it automatically changes directory structure, environmental data, files, versions and syntax.

To begin with, you need to designate input and output path as illustrated below. Then click the Migrate button to start the process.

If a project with the same name already exists in the output path, an alert box will appear, asking you whether to overwrite the existing project.

Once an automatic migration begins, you can see the process through log messages, as illustrated below.

If you want to suspend the process, click the Stop button. If you want to resume, click the Remigrate button.

When the automatic conversion process comes to an end, the message "finished" will be displayed with the numbers of the items that have succeeded or failed in migration. At the same time, the Finish button will be activated.

• If you click the Finish button, the project will be opened in the migration mode after the wizard is closed.

• If you click the Cancel button, Nexacro Studio will do nothing and close the Migration Wizard. The migrated project produced by the wizard will be preserved along with the migration history. When you open the project again later, therefore, you will be asked to continue the migration tasks from where they were left off.

If you have successfully performed the tasks so far, you will find a resulting Nexacro Platform 17-based project in the output path you defined above. Among the directories under the project, there is a log file in the migrate folder, and it contains the information on the results of migration. You should not modify or delete this file since it is essential for the next step where you fix the files that have been failed to be converted.

Fixing Errors

Once you perform a conversion process by using the Migration Wizard, you can open the resulting project in the migration mode. This mode allows you to review the logs of the conversion process, trace the files that have been failed to be migrated and fix the related errors. This error-fixing process is imperative as it helps you solve the problems related to the functions not provided by Nexacro Platform or to user-written codes.

You will take the below steps to fix errors.

1. Check migration log: identify a problematic file, determine which part of it causes an error and figure out how the code was changed from its original.

2. Fix error: analyze the error and fix it. To this end, you need to change the existing code slightly or sometimes even to rewrite it completely.

Check migration log

Migration Log allows you to check the items that have failed to be converted or that contain errors.

Migration Log is organized in a tree structure with each level containing the following information: file information > changes > relevant line. Each item is featured with an icon that is marked with one of the four symbols indicating log types. The below table presents the descriptions of those symbols.

Fix error

You need to think about the solutions for the items that the Migration Wizard has failed to convert. While you can fix some errors with simple changes, other errors may require you to devise different functions as replacements or even to create new files based on Nexacro Platform 17.

Ending Migration Project

When you close or update a migration project, you are asked whether to maintain the migration logs. If you click "Yes", the migration logs will continue to appear next time when you open the project. If you click "No", the migration logs will be deleted while the project will be opened in the project mode.

Migration Mode Menu

After you finish the automatic conversion conducted by the Migration Wizard, you can open the resulting project in the migration mode. This mode consists of the Project Explorer, Migration Log and DiffView. The Project (Migration) Explorer manages the files that are included in a converted project while the Migration Log pane presents the errors that occurred in the process of the automatic conversion. The DiffView pane allows you to compare two versions of source codes—before and after the automatic conversion. With the foregoing tools, you can see the changes made and modify files if necessary.

Project Explorer

The Project Explorer in the migration mode basically functions the same as the Project Explorer in the project mode, which lists the files in a project in the form of a tree. The difference is that the explorer in the migration mode presents the information on migration by using colored file names.

Migration Log

Migration Log presents the results of conducting a migration by giving detains on the changes.

You can see the details on a warning log or information log by expanding the relevant tree.

Migration DiffView

You can open the DiffView editor by right-clicking a certain file from Migration Log and select Show Difference from the context menu.

The below picture shows DiffView opening a file. The original file is on the left pane while the migrated file is on the right pane. Changes are highlighted with blue color.

On the right pane where a migrated file is opened, you can see the information on changes and edit the source codes.