fredriktjarnberg
May 3, 2011
  7204
(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

May 3, 2011 07:27 PM

THanks Fredrik, really appreciate the quick response and feedback!

Please login to comment.
Latest blogs
Removing Unused Properties in Optimizely CMS 13

Learn how to remove orphaned property definitions in Optimizely CMS 13. Explore API updates for IContentTypeRepository and how to safely use...

Stuart | Apr 17, 2026 |

How to Remove the "Paste formatting options" Dialog in Optimizely CMS 12

If you've upgraded from an older Optimizely CMS solution lately, you may have noticed a dialog popping up every time an editor pastes content from...

Henning Sjørbotten | Apr 17, 2026 |

Creating an admin tool - unused assets

Let's make an admin tool to clean unused assets and see how to extend your favorite CMS with custom tools and menues! We will build a tool step by...

Daniel Ovaska | Apr 15, 2026

Running Optimizely CMS on .NET 11 Preview

Learn how to run Optimizely CMS on the .NET 11 preview with a single-line change. Explore performance gains, PGO improvements, and future-proofing...

Stuart | Apr 15, 2026 |