fredriktjarnberg
May 3, 2011
  5804
(2 votes)

CMS 6 R1 and R2 public API diff.

We have gotten a request from Stefan Forsberg to publish a change log of API changes for CMS 6 R2. We are continuously running an internal tool to catch binary breaking changes before they are committed to our repository (as part of our gated check-in build). In order to commit the change the problem needs to be fixed (remove the breaking change) or acknowledged. This removes unintentional breaking changes completely and also reduces intentional breaking changes to a minimum. An acknowledged API diff (marked as “Ignored” in our log) will end up in the release notes document. Note that we are only tracking signature changes (whether a signature (type or member) has been added or removed between two releases). Also note that our tool will not trap the change that was discussed in Stefan’s post since it is not binary breaking change.

So here it is: CMS 6 R2 API changes (compared with CMS 6).

We will look into improving the reporting for upcoming releases maybe using the proposed tool http://inca-app.com/.

May 03, 2011

Comments

Stefan Forsberg
Stefan Forsberg May 3, 2011 07:27 PM

THanks Fredrik, really appreciate the quick response and feedback!

Please login to comment.
Latest blogs
Telemetry correlation for Scheduled Jobs in Optimizely

I previously demonstrated how to correlate telemetry to Azure Application Insights within a Hangfire job. But how about those jobs that are built a...

Stefan Holm Olsen | Mar 23, 2023 | Syndicated blog

Fixing Optimizely Content Syncing/Caching Issues on the DXP pre CMS.Core 12.13.0

Hi all, With our recent deployments to the DXP for .NET 6 projects (one a new build and one an upgrade) our clients had raised issues where there...

Scott Reed | Mar 23, 2023

Handle hostnames, schedule jobs and role access when synchronizing content

The Environment Synchronizer module helps you to set your environment into a known state after synchronizing databases between environments. In thi...

Ove Lartelius | Mar 23, 2023 | Syndicated blog

4 tips and tricks for Hangfire on Optimizely CMS

Here are four useful tricks I always apply to any site where I use Hangfire (code included).

Stefan Holm Olsen | Mar 21, 2023 | Syndicated blog