Magnus Rahl
Oct 19, 2016
  4119
(4 votes)

Planned Breaking Changes in Commerce 2016

As previously announced, new major versions of CMS and CMS UI are coming. Compatible versions of Commerce, Find for Commerce and Service Api will be available from day one. In order to create a compatible version of Commerce, we have to do a small number of low-impact breaking changes in Commerce, which means Commerce too will have a new major version.

The breaking change consists of removing some types that support the Commerce UI (not intended to be used directly) from the EPiServer.Commerce.Core package. The removed types are:

  • EPiServer.Business.Commerce.Providers.ProductSearchProviderBase
  • EPiServer.Business.Commerce.Providers.ProtectedProductSearchProvider
  • EPiServer.Business.Commerce.Providers.ProductSearchProvider
  • EPiServer.Commerce.Catalog.CatalogMetadataExtender
  • EPiServer.Commerce.Marketing.PromotionDataMetadataExtender
  • EPiServer.Commerce.SpecializedProperties.DictionarySelectionFactory
Oct 19, 2016

Comments

Please login to comment.
Latest blogs
The future of Content: Introducing Optimizely CMS 13

Optimizely In the rapidly evolving landscape of digital experience, the "monolithic vs. headless" debate is being replaced by a more sophisticated...

Aniket | May 6, 2026

Hide built in scheduled job from the admin UI

Ok so this probably goes into the not so useful section but late last night I got a veery strong feeling that all projects I am  involved with have...

Per Nergård (MVP) | May 6, 2026

Optimizely SaaS CMS Developer Certification Exam

The Optimizely SaaS CMS Developer Certification is an industry-recognized credential for developers and architects who build scalable, composable...

Megha Rathore | May 5, 2026

Piwik PRO Connector for Optimizely CMS — Now on NuGet (and Yes, It Speaks Both 12 and 13)

Analytics has spent the last decade living in another tab — and what's in that tab usually isn't the full story. Between consent requirements,...

Allan Thraen | May 4, 2026 |