crli
Dec 28, 2009
  6948
(0 votes)

Breaking changes between EPIServer 6 CTP2 and Release Candidate

Rather than enumerating every change between preview 2 and the release candidate we downloaded a few of the winning gadgets and made the required changes to make them work on the RC version.

This is the list of changes. Please feel invited to share any other breaking change that isn't listed here.

1. On the client, the gadget instance is passed directly instead of gadgetContext which has been removed

// from
function fcsm_initialize(e, gadgetContext) {
    fcsm_gadgetInstance = gadgetContext.instance;
// to
function fcsm_initialize(e, gadget) {
    fcsm_gadgetInstance = gadget;

2. The extensions in Shell Extensions now lives somewhere else

// from
<%@ Import Namespace="EPiServer.Shell.Extensions" %>
// to
<%@ Import Namespace="EPiServer.Shell.Web.Mvc.Html" %>

3. The dynamic data store has gained a factory

// from
DynamicDataStore<ReportSettings> store =
    DynamicDataStore<ReportSettings>.CreateStore("AnalyticsGadgetStore", false);
// to
DynamicDataStore store =
    DynamicDataStoreFactory.Instance.GetStore("AnalyticsGadgetStore")
    ?? DynamicDataStoreFactory.Instance.CreateStore("AnalyticsGadgetStore",
                                                    typeof(ReportSettings));

4. The dynamic data store “Find” has changed

// from
store.Find("GadgetId", gadgetId).FirstOrDefault<ReportSettings>();
// to
store.Find<ReportSettings>("GadgetId", gadgetId).FirstOrDefault();

5. The dynamic data store LINQ has changed

// from
from alertCollection in store
     where …
     select alertCollection;
// to
from alertCollection in store.Items<AlertMethodCollection>()
     where …
     select alertCollection

6. The gadget contracts namespace has moved

// from
using EPiServer.Shell.Gadgets.Contracts;
// to
using EPiServer.Shell.Gadgets;

7. Some resource texts have been moved

// from
[GadgetAction(ActionType.Menu, TextResourceKey = "Edit",
    ResourceType = typeof(EPiServer.Shell.UI.Views.Shared.SharedResources))]
// to
[GadgetAction(TextResourceKey = "Edit",
    ResourceType = typeof(EPiServer.Shell.Resources.Texts))] 

8. The configuration has changed to reflect that we now split modules by protected and public (added december 30)

// from
<episerver.shell>
  <siteSettings rootPath="~/U/" />
  <modules autoDiscovery="Minimal">
    <add name="DdsExplorer">
      <assemblies>
        <add assembly="DdsExplorer" />
      </assemblies>
    </add>
  </modules>
  <frameworkModules>
    <add name="Shell">...</add>
    <add name="CMS">...</add>
  </frameworkModules>
</episerver.shell>
// to
<episerver.shell>
  <protectedModules rootPath="~/U/">
    <add name="Shell" />
    <add name="CMS" />
  </protectedModules>
  <publicModules rootPath="~/public/" autoDiscovery="Minimal">
    <add name="DdsExplorer">
      <assemblies>
        <add assembly="DdsExplorer" />
      </assemblies>
    </add>
  </publicModules>
</episerver.shell>

9. Some style classes have a different name (added december 30)

//from
<div class="epi-defaultPadding">
<div class="epi-smallPadding">
//to
<div class="epi-padding">
<div class="epi-padding-small">

 

I also took the liberty of uploading the changes to codeplex. I take no responsibility for the quality of any gadget or any introduced errors. All credits goes to the original author. These are the gadgets that were updated:

Let me know right away if a gadget needs to be removed or if you need access to change a release.

Dec 28, 2009

Comments

Please login to comment.
Latest blogs
Optimizely CMS 12 Now Fully Supports .NET 10

This is the latest installment in our ongoing series covering .NET version support for Optimizely products. If you've been following along, you may...

Bien Nguyen | May 25, 2026

Optimizely Opal: How to Build Effective Workflow Agents

If you're building workflow agents in Optimizely Opal, this post covers how specialized agents pass context to each other, why keeping agents small...

Andre | May 20, 2026

ReviewPR: An Azure Function That Reviews Your Azure DevOps Pull Requests With Claude

A while back I wrote about an  Azure Function App for PDF creation that we use to offload PDF rendering from our Optimizely DXP site. That same...

KennyG | May 19, 2026

Accelerating Optimizely CMS and Commerce upgrades with agentic AI (Part 2 of 2)

The Real Transformation in Optimizely CMS 13: Why the Upgrade Itself Is the Easy Part. A field-tested playbook for enterprise teams moving from...

Hung Le Hoang | May 18, 2026