Configure the code upgrade service in Lifecycle Services (LCS)
This topic explains how to configure the Code upgrade tile in Lifecycle Services (LCS) to migrate your solution to the latest version of Dynamics 365 for Finance and Operations.
The code upgrade tool operates by connecting to Visual Studio Team Services (VSTS), locating your Trunk\Main branch, branching to a new branch which will be named as Releases\<version number>, and then performing the code upgrade there. After this process is complete you can synchronize your Finance and Operations developer environment to this new branch under Releases\<version number> and resolve conflicts. When you have compiled and tested your upgraded code you can merge the new branch back into Trunk\Main, using source control explorer in Visual Studio and the process is complete.
Dynamics 365 for Finance and Operations version 8.0 and newer, does not allow customization via overlayering of Microsoft models. Before you upgrade, you must have have a plan to refactor your customizations into extensions. For more information, see the Extensibility homepage and Refactor overlayering on 8.0 environments.
Create the Trunk\Main folder structure
For the code upgrade service to recognize your source code, the folder structure must conform to the following strict pattern. The correct structure is:
- For code itself: ..\<VSTS project name>\Trunk\Main\Metadata
- For Visual Studio projects: ..\<VSTS project name>\Trunk\Main\Projects
To create new folders in VSTS, create the folders locally and then check them into VSTS.
Folder names are case sensitive, that is, you must use Main and not MAIN, or the code upgrade service will not recognize the folder.
To create a personal access token
To connect to a VSTS project, LCS is authenticated using a personal access token. Use the following steps to create a personal access token in VSTS. If you have already configured your LCS project to connect to your VSTS project, you can skip this section.
Sign in to visualstudio.com and locate your VSTS project.
In the top right corner, hover over your name, a menu appears, select Security.
Click Add to create a new personal access token, give it a name, and then enter the amount of time that you want the token to last for. Click Create Token.
Copy the token to your clipboard. You will not be able to find the token details after this step is completed, so be sure that you have copied the token before navigating away from this page.
Configure your Lifecycle Services project to connect to VSTS
In your LCS project, go to the Project settings tile, select Visual Studio Team Services, and then select the Setup Visual Studio Team Services button. This configuration is needed by many LCS tools, if you have already configured LCS to connect to your VSTS project, you can skip this section.
Enter the root URL for your VSTS account and the access token created earlier, and then click Continue.
On the Review and save page, click Save.
Create an ax7.version file
The code upgrade tile in LCS automatically finds the version of Finance and Operations that you are migrating from, by reading the ax7.version file under the Main folder in your source control. You must create this file manually, either in Visual Studio or through the VSTS portal, as shown below. This file is not needed if you migrated your code from Dynamics AX 2012 R3 or an earlier version. The version number entered here must be the application version (not the platform version). Take care to enter the correct version number here as entering an incorrect version number in this file may cause your code upgrade run to fail.
For more information about how to identify which application version you have, see Overview of Microsoft Dynamics AX build numbers.
Execute the code upgrade tile
In your LCS project, select the Code upgrade tile.
In the bottom left corner of the screen, click Add, and then enter a name and description. Select the version you are upgrading from as Microsoft Dynamics AX 7, and then click Create.
- If you are upgrading your code from Dynamics AX 2012 R3, select the version you are upgrading from. You will be prompted to upload a zipped version of your Dynamics AX 2012 R3 model store file.
- If the Estimation Only check box is selected, the tool only generates a report and does not check in or create a new code branch in VSTS for you. You should use this option if you want to evaluate the potential size of the work involved in upgrading before you commit to the actual upgrade.
Click Analyze code in the bottom right corner. The code upgrade process will start. This typically takes 40 minutes for a large solution to complete. When complete, return to the Code upgrade tile in LCS to view the results.
The code upgrade service creates a new branch and checks in the upgraded code to your VSTS project. After the upgrade process is complete, your code will exist in a new branch under the Releases folder. The branch name is suffixed with the date and time of the upgrade.
Merge Releases back into Trunk\Main
Once the upgraded code in Releases\<version number> compiles sucessfully and has passed your tests, then you are ready to merge this branch back into Trunk\Main. To do this, on your development environment in Visual Studio open the Source control explorer pane then right-click on the Releases\<version number> branch and in the context menu go to Branching and Merging and then on the sub-menu select Merge.
This will open the Source Control Merge Wizard which will guide you through merging the Releases\<version number> branch back into Trunk\Main.