Per Bjurström
Jul 2, 2015
  4137
(10 votes)

Planned breaking changes 2015

An update to let you know what breaking changes we are doing in CMS later this year. For many sites the changes will go unnoticed, just another major version number, the latest version of the Alloy templates for example requires no code changes - just recompile and you are done.

Breaking Changes

  • Remove hard dependency on Log4Net. This will make it possible to run on the latest version of Log4Net or use another provider. Link to SDK.
  • As previously announced we will remove our implementation of WWF (Windows Workflow Foundation), where WWF 3 that we are using is now obsoleted and (officially) not supported on Azure. We are instead investing in "Projects 2.0" and you can follow the release feed to see this beta feature light up and support rich collaboration on not just pages but block, media and catalog content.
  • Remove remains of the VPP system that was obsoleted in CMS 7.5. Link to SDK.
  • Remove Content Channel and the other ASP.NET 2 Web Services that was last shipped in 7.5 and officially obsoleted in 8.
  • Remove assemblies EPiServer.BaseLibrary.dll and EPiServer.Implementation.dll. These assemblies was the framework of CMS 5 and contained internal features such as the ObjectStore. There are a few classes in there still used that are being moved to EPiServer.dll.
  • Remove Page Objects. A feature that pre-dated blocks. Obsoleted in 7.5.
  • Disable Dynamic Properties by default. As officially annonced in 7.5 this feature does not support the new user interface. We know there will be a lot of sites upgrading that are using dynamic properties so it will be left intact and there will be a setting to enable/disable this feature.

Release later this year with more details. See this post by Magnus for updates on planned breaking changes in Commerce.

Jul 02, 2015

Comments

valdis
valdis Jul 2, 2015 09:48 AM

Great that log4net will be removed! What about reference to log4net in EPiServer.Logging.Log4Net? Will that be updated or still remain with 1.2.10?

What about StructureMap version in EPiServer.Framework?

What about DotNetZip version in EPiServer.CMS.UI.Core?

Jul 2, 2015 11:37 AM

The dependency from EPiServer.CMS.Core to EPiServer.Logging.Log4Net will be removed. We will also release a v2 of EPiServer.Logging.Log4Net. That makes sure we support both v1 and v2 of the Log4Net packages and any other logging provider.

StructureMap 3 is not signed so we can't take that dependency, we don't have a good solution to this right now.

Removing DotNetZip from EPiServer.CMS.UI.Core is on the backlog, don't know when it will be fixed.

henriknystrom
henriknystrom Jul 3, 2015 12:02 AM

Seems like there might be a signed version to the StructureMap 3 coming in the near future, so there may be some hope on that front after all!

Sep 15, 2015 05:12 PM

DotNetZip was dropped and StructureMap was upgraded to 3. Happy days :)

Please login to comment.
Latest blogs
Optimizely SendGrid SMTP host is deprecated

SendGrid is a services for sending email that is included in Optimizely DXP. Previously smtp.episerver.net was the recommended SMTP server to use,...

Tomas Hensrud Gulla | Dec 4, 2022 | Syndicated blog

Hosting Optimizely CMS 12 on Docker Engine

Since Optimizely CMS can now be deployed as a Docker container, here is a demonstration of building, running and scaling an Optimizely CMS 12 site ...

Stefan Holm Olsen | Dec 4, 2022 | Syndicated blog

How to use CacheTagHelper with content areas in Optimizely CMS 12

I might be going out on a limb here - if you have a better solution, feel very free to share it!  Upgrading your Optimizely web application from .N...

Andreas J | Dec 2, 2022

The 1001st Piece in your 1000 Piece Puzzle: .NET Default Interface Functions

I was recently working with a client who wanted a reasonably large subsystem added to Optimizely that would add automated management to their...

Greg J | Nov 28, 2022 | Syndicated blog