These packages have their own version number and may or may not be upgraded together with the core CMS packages.
- EPiServer.CMS.AspNet + EpiServer.Framework.AspNet
The NuGet packages EPiServer.CMS.AspNet and EPiServer.Framework.AspNet contain all APIs related to web development on the ASP.NET stack (both MVC and WebForms). Existing namespaces are preserved to keep the upgrade as smooth as possible. These packages should be installed automatically.
A new NuGet package, EPiServer.ServiceLocation.StructureMap, contains the integration with StructureMap, and has support both for the existing signed StructureMap 3 and the new unsigned StructureMap 4 (coming in version 2 of EPiServer.ServiceLocation.StructureMap). The package only contains the integration and has NuGet dependencies on the official StructureMap packages. This package should be installed automatically.
Optimizely and module packages should not depend directly on this package but use the abstractions for dealing with dependency injection. This API has been available for a few versions and is already being used by most Optimizely products.
A new NuGet package, EPiServer.CMS.TinyMCE, contains the rich-text editor. This package will be installed automatically if you have a dependency on EPiServer.CMS.
- EPiServer.Search.Cms (optional)
The CMS integration for full-text search has been moved to a separate NuGet package, EPiServer.Search.Cms. Previously, this implementation was found in the assembly EPiServer.ApplicationModules shipped with NuGet package EPiServer.Framework. For websites using DXP and Optimizely Search & Navigation, these packages do not have to be installed, and any configuration related to the built-in search (episerver.search in web.config) can be removed.
- EPiServer.XForms (optional)
The XForms functionality was previously deprecated and is superseded by Optimizely Forms. XForms have been moved to a separate NuGet package, EPiServer.XForms. If the website is using XForms, you should manually install this package or migrate to Optimizely Forms.
- EPiServer.DynamicContent (optional)
The Dynamic Content functionality has previously been deprecated and is superseded by blocks. Dynamic Content has now been moved from the platform to a separate NuGet package, EPiServer.DynamicContent. If the website is using Dynamic Content, you should manually install this package or migrate to blocks.
Updated about 2 months ago