Area: Optimizely Commerce
Applies to versions: 13

Upgrading to Commerce 13

Recommended reading 

Following semantic versioning, Optimizely Commerce 13 is a new major version containing some incompatible API changes. This section describes breaking changes introduced in Commerce 13, and what you need to do 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. 

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

Last updated: Mar 25, 2019

Recommended reading