Uppgrading to #Episerver CMS 11 causing errors and how to solve them

Big changes under the hood this time, mostly classes being moved out to new binaries, meaning many add ons / dependencies needs to be updated.

Published 22nd November 2017
Episerver CMS 11.1

Beware AddOn developers, your addon must be updated

The CMS Core team is now targeting .NET 4.6.1 in order to be compliant with NetStandard 2.0, therefor has moved a lot of ASPNET related to new Nuget Packages, mainly EPiServer.CMS.AspNet + EpiServer.Framework.AspNet + EPiServer.ServiceLocation.StructureMap. Check hole list: http://world.episerver.com/documentation/upgrading/Episerver-CMS/cms-11/new-nuget-packages/

At the time writing Episerver addons like Episerver Find, Forms, Commerce, ImageVault are not released/compatible.

Related Errors:

App_Code.0.cs: error CS1519: Invalid token ‘,’ in class, struct, or interface member declaration

If you are using the obsolete Subscription system, this API has been moved to EPiServer.CMS.AspNet

And when site uses a custom profile whose properties are defined under system.web, profile, properties in the config file. The type of one of the properties SubscriptionInfo is specified in the “Namespace.ClassName, AssemblyName” format. This Error is hard to find, and it shows up on runtime init.

Eg Change in web.config


TypeLoadException: Could not load type EPiServer.Web.Routing.IContentRouteHelper from assembly EPiServer, Version=, Culture=neutral, PublicKeyToken=8fe83dea738b45b7.

Check the stack trace what is causing this, probably it is an add on, or a dependency that still point at the old CMS 9,10 DLLs. These addons has to be upgraded.

Check Nuget feed if they are update already, if not, contact the author on the project site, or why not help out upgrading, and commit a pull request.

Meanwhile, while trying, you can Either remove these addons, or remove by not scanning them:


This blog post will be updated …

SEO terms
  • Upgrading Episerver CMS 11
  • Undantagsinformation: System.TypeLoadException: Det gick inte att läsa in typen EPiServer.Web.Routing.IContentRouteHelper från sammansättningen EPiServer, Version=, Culture=neutral, PublicKeyToken=8fe83dea738b45b7.
Like it? please up vote