London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
AI OnAI Off
London Dev Meetup Rescheduled! Due to unavoidable reasons, the event has been moved to 21st May. Speakers remain the same—any changes will be communicated. Seats are limited—register here to secure your spot!
Do you have any 3rd parties assembly hanging around? They might be the culprit?
Also make sure you have the correct binding redirect in web.config
After following al upgrade steps from https://world.episerver.com/documentation/upgrading/Episerver-CMS/cms-11/breaking-changes-cms-11/to upgrade from CMS 10 to CMS 11, but I keep getting the following exception on trying to access the CMS via the browser:
Could not load type 'EPiServer.Web.InitializationModule' from assembly 'EPiServer, Version=10.0.1.0, Culture=neutral, PublicKeyToken=8fe83dea738b45b7'.
It seems that some code tries to load the type InitializationModule from the wrong assembly, as this specific type was moved from EpiServer.dll to EPiServer.Cms.AspNet, according to the upgrade documentation: EPiServer.Web.InitializationModule has been moved to EPiServer.Cms.AspNet assembly...
Still same issue.
Any ideas are welcome.