Breaking changes for Commerce Connect 14

The Commerce Administration view is an administrative application replacing the legacy Commerce Manager administration backend system. The new user interface provides a unified and improved user experience.

The Admin view provides support for working with markets, warehouses, catalog indexing, tax configuration, shipping, and payments.

Due to the removal of Commerce Manager, ​the following tasks are now managed through the API:

The Mediachase.BusinessFoundation assembly was also removed as it was mainly used to support Commerce Manager.

Support for the various configuration files in the Configs project folder was removed. The functionality was replaced with the use of Options classes, where you can configure settings in the appSettings file or use the ConfigureServices of the Startup class to override default values for Options. This provides a unified way of configuration methods in ASP.NET Core. See Option configuration classes.

The support for ASP.NET Membership Provider was removed. Only ASP.NET Identity Provider is supported for Optimizely Commerce Connect. See Security and Migrating from SQL membership to ASP.NET identity.

Mediachase.Commerce.Plugins.Payment was removed because it does not support AuthorizeNet. The library is no longer supported in ASP.NET Core.

Support for payment providers PayPal, DIBS, Datacash, and gift card was removed. The CreatedCardPayment class was marked as obsolete and will be removed later. It is strongly recommended that you adopt a PCI-compliant solution for managing payments in your project.

Support for Mediachase.Search.Solr35SearchProvider and Mediachase.Search.SolrSearchProvider packages has been removed. As a replacement, you can use the LuceneSearchProvider or FindSearchProvider. There is in-built support for FindSearchProvider in the Optimizely DXP cloud service environments. See Search.

The Mediachase.MetaDataPlus.Import.Parser.OleDbIncomingDataParser has been removed, and parsing of files using OleDb connection is not supported. CSV and XML data parsers are still supported.

The UserTimeZone functionality was removed from Mediachase.BusinessFoundation.Data to avoid dependency on Windows OS.

You can no longer access the Catalog subsystem through web service calls.

The following changes were done:

Some ASP.NET Core built-in types are no longer binary serializable. NumberFormatInfo is one example. Since serializable Commerce Connect types like Money and Currency use NumberFormatInfo, these also become unserializable. This is considered a breaking change for solutions that rely on binary serialization of these types, meaning that probably SerializationExceptions is thrown.

To make upgrading easier, there is an upgrading tool available. See the Upgrade assistant article.