Area: Optimizely Commerce

Upgrading to Commerce 14

Recommended reading 
Note: This documentation is for the preview version of the upcoming release of CMS 12/Commerce 14/Search & Navigation 14. Features included here might not be complete, and might be changed before becoming available in the public release. This documentation is provided for evaluation purposes only.

This section provides an overview of breaking changes introduced in Commerce 14, and the main areas affected when upgrading from previous versions.

What is a breaking change?

A breaking change is one that might cause other components to fail. When a breaking change is made to the signature of a method/class/interface, the old signature is often kept intact but set as obsolete and may cause a warning in Visual Studio. As long as the Visual Studio project setting "Treat Warnings as Errors" is disabled in Visual Studio, you can postpone fixing these warnings.

Classes that expose constructors which take dependencies are normally deleted without an obsolete warning in major releases, since the compiler gives enough information about what to change. Keeping them complicates dependency injection, since there are multiple constructors to choose from which, over time, might or might not overlap.

In each major version, obsolete methods are removed permanently to make sure that the API is kept clean and usable over time. So, even if you can postpone fixing warning messages, it is good practice to fix all warning messages before upgrading to a major version. 

See Breaking changes (Commerce 14).

Upgrading support

To make upgrading to Commerce 14 easier, there is an upgrading tool available, see Upgrade assistant.

Do you find this information helpful? Please log in to provide feedback.

Last updated: Jul 02, 2021

Recommended reading