Skip to main content
Optimizely Academy

End-user eLearning

Upcoming events

Certification

Partner training

Community

All Topics

CMS 11 VS CMS 12

  • By Optimizely Education
  • Published: Feb 2, 2026
  • Rating
    Average rating: 0 No reviews

Outline
At a glance:
  • CMS 11: ASP.NET 4, Windows/IIS, WebForms + MVC
  • CMS 12: ASP.NET Core, cross-platform, Razor Views only, modern PaaS-ready
  • Focus: Architecture, rendering, DI, configuration, authentication, headless support

Introduction

Understanding the evolution from CMS 11 to CMS 12 is essential for developers. CMS 12 introduces a significant architectural shift by moving to ASP.NET Core, offering modern performance, cloud readiness, and simplified development workflows. This guide highlights key differences in architecture and rendering approaches.

1. Key Architectural Differences

The biggest shift is the framework foundation. Below are the core areas where CMS 11 and CMS 12 diverge architecturally.

Architectural Comparison

Select a topic to expand and read the details.

1.1 Framework Foundation: ASP.NET 4 vs. ASP.NET Core ▼
  • CMS 11: Built on ASP.NET 4 (.NET Framework). Windows-only, hosted on IIS, reliant on older libraries.
  • CMS 12: Built on ASP.NET Core (.NET 6+). Cross-platform, high-performance, open-source.
  • Implications: Runs on Windows, Linux, and macOS. Supports Docker. Provides streamlined development and access to the latest .NET libraries.
1.2 Application Startup and Configuration ▼
  • CMS 11: Startup via Global.asax and OwinStartup. Configuration managed in web.config (XML).
  • CMS 12: Unified Program.cs handles all startup. Configuration lives in appsettings.json, environment variables, and other modern providers.
1.3 Dependency Injection (DI) ▼
  • CMS 11: Optional DI via third-party containers (StructureMap, Unity).
  • CMS 12: Uses the native ASP.NET Core DI container. Enables seamless registration of Optimizely services, promoting modular and testable code.
1.4 Logging and JSON Serialization ▼
  • CMS 11: Logging via log4net or NLog; JSON serialization via Newtonsoft.Json.
  • CMS 12: Logging via Microsoft.Extensions.Logging; JSON via System.Text.Json by default for better performance.
1.5 Authentication ▼
  • CMS 11: ASP.NET Identity paired with OWIN middleware.
  • CMS 12: OpenID Connect (OIDC), commonly with Azure AD / Microsoft Entra ID, aligning with modern cloud security standards.
1.6 NuGet Packages and API Compatibility ▼
  • CMS 11: Packages targeting .NET Framework.
  • CMS 12: Requires .NET Standard 2.0 or .NET 6+ compatible packages. Some breaking changes arise from the ASP.NET Core migration; careful review is needed during upgrade.

2. Key Rendering Differences

Rendering approaches evolved significantly between the two versions. Here are the core areas where they differ.

Rendering Comparison

Select a topic to expand and read the details.

2.1 View Engines and Rendering Methods ▼
  • CMS 11: Supported both ASP.NET WebForms and MVC (Razor Views).
  • CMS 12: WebForms support removed. Razor Views only. Rendering is fully aligned with ASP.NET Core conventions, resulting in a streamlined and consistent approach.
2.2 Headless Capabilities ▼
  • CMS 11: Limited headless support; more custom development required to serve content to front-end clients.
  • CMS 12: Full headless support with comprehensive REST APIs, SDKs, and multi-channel content delivery. Compatible with React, Vue, Angular, or any other front-end or back-end consumer.
2.3 Block Controllers to View Components ▼
  • CMS 11: Blocks rendered using dedicated MVC controllers.
  • CMS 12: Shift toward View Components or simpler reusable patterns, following ASP.NET Core best practices for encapsulation and reusability.

3. Implications for Developers

Migrating from CMS 11 to CMS 12 involves several concrete actions across your codebase and project configuration:

  • Migrate Project Files: Update .csproj to target .NET 6+ and update all NuGet package references accordingly.
  • Refactor Startup Logic: Adapt Global.asax / Startup.cs patterns to the unified Program.cs model.
  • Update Configuration: Move from web.config to appsettings.json and environment variables.
  • Address Breaking Changes: Identify and fix API changes introduced by the ASP.NET Core migration and updated Optimizely packages.
  • Remove WebForms: Convert existing WebForms views to Razor Views.
  • Re-evaluate Integrations: Ensure all third-party libraries are compatible with ASP.NET Core before upgrading.

Pro tip: The migration effort pays dividends quickly. Benefits include better runtime performance, improved security posture, cross-platform deployment flexibility, and a modern development workflow aligned with the broader .NET ecosystem.

Conclusion

Optimizely CMS 12 is a leap forward, fully embracing ASP.NET Core. The migration from .NET Framework fundamentally changes how applications are built, configured, and deployed — delivering performance, flexibility, and cloud-readiness as first-class outcomes. Developers gain modern startup patterns, simplified configuration models, and streamlined rendering workflows, making CMS 12 a future-proof platform for building powerful digital experiences.