Migrate the Retail SDK from Visual Studio 2015 to Visual Studio 2017
Support for the Retail SDK will end in October 2023. Please use or migrate to the Commerce SDK, which provides several benefits including a simplified development and update experience, and improved performance.
This article explains what has changed in the 10.0.11 release of the Retail software development kit (SDK), how to migrate it to Visual Studio 2017, and how to update an extension project reference library to NuGet.
What has changed in the 10.0.11 release
- The Retail SDK has been updated to Visual Studio 2017.
- References have been updated to PackageReference (NuGet package reference).
Retail SDK updated to support Visual Studio 2017
The Retail SDK now runs on Visual Studio 2017. In release 10.0.11 and later, all Retail SDK components, including Modern POS (MPOS), Cloud POS (CPOS), the Commerce runtime (CRT), Headless Commerce, the proxy, and Hardware station (HWS), can be built and compiled only in Visual Studio 2017. You can't use Visual Studio 2015.
References updated to PackageReference
The Retail SDK reference libraries use PackageReference. All the SDK samples use the PackageReference model. All the SDK reference libraries are converted to NuGet packages, and libraries are removed from the RetailSDK\Reference folder. The NuGet packages are in the ..\RetailSDK\Code\pkgs or ..\RetailSDK\pkgs folder. The following example shows the reference to Microsoft.Dynamics.Commerce.Runtime.
<PackageReference Include="Microsoft.Dynamics.Commerce.Runtime" Version="9.21.x" />
What is affected
- If you want to deploy a new merged package (that is, an extension and out-of-box changes) on version 10.0.11 or later, you must migrate your solution to the SDK on Visual Studio 2017. No code changes are required to migrate and build your solution.
- Hard-coded references in extension projects must be migrated to PackageReference (NuGet reference).
Migrate to the SDK for Visual Studio 2017
There are two ways to migrate:
Deploy a new development and build environment from Microsoft Dynamics Lifecycle Service (LCS), and manually install the Visual Studio 2017. Starting with version 10.0.13, the VHD templates that you use to provision developer and test environments will include Visual Studio 2017. For more information, see Visual Studio 2017 requirements for X++.
Update extensions to Visual Studio 2017 in an existing development environment:
Install Visual Studio 2017 Community, Professional, or Enterprise edition on the existing build and development virtual machine (VM) with the following workloads:
- .NET Desktop development
- Universal Windows Platform development
- ASP.NET and web development
- Azure development
- Node.js development
- .NET Core cross-platform development
- Mobile development with .NET (required for hybrid app development)
If you manually install Visual Studio 2017, install the following prerequisites on the development VM. If you don't install these prerequisites, compilation will fail, and .NET SDK and runtime errors will be generated:
In Visual Studio, go to Tools > Get Tools and Features. Select the Individual components tab and select the TypeScript 2.2 SDK from SDKs, libraries, and frameworks section and install it. Visual Studio 2017 has Typescript 3.1 as the default. You also need to include 2.2.2 because the POS app is based on Typescript 2.2.2.
If the SDK compilation fails with the following error message, "The current .NET SDK does not support targeting .NET Standard 2.0", try installing the x86 version of the .NET 2.1 SDK and runtime.
Build the Retail SDK
Follow these steps to build the Retail SDK.
- Open the Developer command prompt for Visual Studio 2017 or the MSBuild 15.0 command prompt. Build the out-of-box Retail SDK by running msbuild /t:rebuild from the root of the SDK folder (where you can find the dirs.proj file). The folder is RetailSDK\dirs.proj or RetailSDK\Code\dirs.proj in most installations.
- Merge your extension to the new SDK folder. For information about how to merge extension with the SDK, see Upgrade the Retail channel extension to the latest Retail SDK.
- After the extensions have been merged, update all the hard-coded references to PackageReference by using the NuGet packages.
Update the reference in the CRT and Headless Commerce extension projects
- Use any of the sample CRT projects in the Retail SDK (..\RetailSDK\SampleExtensions\CommerceRuntime) as a template and migrate your CRT extension to this new format. The new samples uses the Visual Studio 2017 formats for project dependencies (NuGet references).
In the NuGet Package Manager, add the local NuGet repository folder. For information about how to create a local NuGet repository, see Install and manage packages in Visual Studio using the NuGet Package Manager.
All the SDK reference libraries are converted to NuGet packages, and libraries are removed from the RetailSDK\Reference folder. The NuGet packages can be found in the ..\RetailSDK\Code\pkgs or ..\RetailSDK\pkgs folder.
To add the NuGet package reference to the project, right-click the Dependencies node in the project, and then select Manage NuGet Packages.
In the NuGet Package Manager, add the required packages. For example, if the project requires the CRT library reference, add the Microsoft.Dynamics.Commerce.Runtime NuGet package. After the NuGet package reference is added, the project file will be updated with the package reference, as shown in the following example.
<ItemGroup> <PackageReference Include="Microsoft.Dynamics.Commerce.Runtime" Version="9.21.x" /> </ItemGroup>
PackageReference also supports floating versions, where the version is updated with the floating version number. For more information about floating versions, see How NuGet resolves package dependencies. When the floating version is used, extensions no longer have to update the reference for every update, because NuGet will automatically resolve to the latest version. For example, the package reference might resemble <PackageReference Include="Microsoft.Dynamics.Commerce.Runtime" Version="9.21.x" />.
In a similar way, update the references for all the Headless Commerce APIs, proxy, and Hardware station extension projects.
Headless Commerce APIs and Proxy extensions
Migrate the Headless Commerce APIs and Proxy extensions to the new extension model released in version 10.0.12. Starting in version 10.0.12, the same Headless Commerce extension library can be used for offline use, no separate C# proxy library is needed, however a client typescript proxy is still required. For more information, see Create a new Headless Commerce extension API. This step is recommended but not required, as the Headless Commerce and proxy extension libraries will continue to work until the old extension model is deprecated.
What isn't affected
You don't have to change the extensions code that was written in previous versions of the Retail SDK. You must update references and recompile only for the new SDK.
If you have existing pipelines in Azure Pipelines not based on build machine agent that are set up for the Retail SDK build will continue to work. In the MSBuild task step, change the MSBuild version to 15.0, if this change is required.
Follow the steps to set up a build pipeline in Azure DevOps without using build VM and build agent from the build machine. For more information, see Set up Commerce SDK build pipeline.
Azure DevOps pipeline using build machine agent
The same build machine used for MSBuild with the Azure DevOps pipeline can be used with SDK version 10.0.11. Perform the following steps on the build machine for the SDK:
- Install Visual Studio 2017 on the build machine.
- Optionally, run msbuild (msbuild version 15.0) from the developer command prompt for Visual Studio 2017 on the build machine. Open the developer command prompt for Visual Studio 2017 and navigate to the Retail SDK root folder. Type msbuild dirs.proj and make sure that the MSBuild completes successfully.
- On the build machine, add an environment variable for the MSBuild 15.0. Go to System Properties > Environment Variables > System variables. Select the Path variable, and then select Edit. In the Edit environment variable window, select New and add the path variable for MSBuild 15.0. Move it to the top of the list of PATH variables. For example, the path will be something like - C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\MSBuild\15.0\Bin. The path will change based on where you installed Visual Studio 2017. To get the path for MSBuild from the developer command prompt for Visual Studio 2017, type where MSBuild.
- To validate the config information
- Open a regular "CMD" window (not the Visual Studio command prompt).
- Run msbuild /version.
- Verify that the first result in the list is MSBuild version is 15.9.* or greater.
- Restart the Azure DevOps build agent on the build machine.
- In Azure DevOps pipeline, change the MSBuild version to 15.0 or later.
If the build from Azure DevOps pipeline fails with a NuGet error, the Azure Pipeline may not be not using MSBuild version 15.0 for NuGet restore or the extension projects are not upgraded to use the package reference model.