Try our conversational search powered by Generative AI!

fredriktjarnberg
Jul 1, 2014
  5020
(5 votes)

.NET 4.5 and the EPiServer platform

Background

.NET 4.5 has been around for quite some time now and a lot of EPiServer projects are running on it already. In addition to .NET 4.5, there are two “dot” releases that supersedes it i.e. .NET 4.5.1 and 4.5.2. .NET 4.5 and its successors are in-place, backward compatible upgrades of .NET 4 which is the lowest version required by the EPiServer 7.5 platform. We have been limiting ourselves to stay on the .NET 4.0 version yet supporting .NET 4.5 leaving the decision to the partner project which version to build the solution on. Now we have come to a point where we think that new features in the EPiServer platform could really benefit from some of the things introduced in .NET 4.5. The most urgent one being the web socket support or more specifically SignalR which we want to use for building better user experiences.

What does this mean for someone taking a dependency on an EPiServer package?

Our plan for introducing this change is by updating our own dependencies to .NET 4.5 and ship that as a minor update i.e. 7.x. For a customer project this means that you will have a backward compatible update of the EPiServer packages which only need a recompilation after being updated. The only case where you need to do more is if your solution is deployed in a .NET 4.0 environment. In that case that environment needs to be upgraded to .NET 4.5 for the site to work.

How can you prepare?

The change is not that dramatic but if you want to be in the best position when this change comes we recommend building for .NET 4.5.2 right away. This forces the development, test and production environments to be prepared when the .net dependency version switch is integrated into the solution. If you are leveraging SignalR in your customer project we also recommend you to align that dependency to work with .NET 4.5.

Jul 01, 2014

Comments

Henrik Fransas
Henrik Fransas Jul 1, 2014 08:00 PM

In the documentation for workflows (http://world.episerver.com/Documentation/Items/Developers-Guide/EPiServer-CMS/7/Workflows/Workflows/) you say that it will be changed when you go to .NET Framework 4.5, what are the plans for that?

Great with going to 4.5, been longing for that

Please login to comment.
Latest blogs
Change the IP HTTP Header used for geo-lookup in Application Insights

.

Johan Kronberg | Jun 10, 2024 | Syndicated blog

Copying property values

In this article I’d like to show simple Edit Mode extension for copying property values to other language versions. In one of my previous blogposts...

Grzegorz Wiecheć | Jun 8, 2024 | Syndicated blog

Auto-translate with OpenAI GPT-4o in Optimizely CMS

Improvements for Episerver.Labs.LanguageManager! It's now possible to auto-translate both a page and its children at the same time! Additionally, m...

Tomas Hensrud Gulla | Jun 7, 2024 | Syndicated blog

Upgrade To Optimizely CMS 12 Issue: List item fields have become Required

There are many funny details to be aware of when upgrading from Episerver CMS 11 to Optimizely CMS 12. One of them that might feel a bit confusing ...

Allan Thraen | Jun 7, 2024 | Syndicated blog

Integrating Apple Pay within Optimizely - Lesson's Learned

Hello Optimizely world, I have recently undertaken the responsibility of assisting our client in the integration of Apple Pay onto their website...

Silvio Pacitto | Jun 6, 2024

A day in the life of an Optimizely Developer - Introduction to Optimizely SaaS Core

What is SaaS Core Optimizely SaaS Core is a cloud-based, headless, and API-first version of the Optimizely CMS (Content Management System) and...

Graham Carr | Jun 4, 2024