NuGet package families in CMS
Package families are groups of Optimizely NuGet packages that relate to each other and release together. They share the same version number and depend strictly on other packages within the same family. For example, the EPiServer.CMS.AspNetCore.HtmlHelpers package and the EPiServer.CMS.Core package are part of the same family, and they depend directly and indirectly on the EPiServer.Framework package.
When Optimizely releases a package family version, release notes and bug fixes are documented with the family name, not individual packages. The feature or fix you need could be in any package in the family, so update them together. Typically, updating one or two top-level dependencies, such as the EPiServer.CMS package, is enough because the rest resolve automatically. If you encounter dependency conflicts, see Resolve NuGet dependency conflicts.
- 📘 Note CMS 13 no longer depends on Castle.Windsor. Applications should use the ASP.NET Core dependency injection container.
- The EPiServer.Cms.HealthCheck package was removed. SQL health checks are now provided through the EPiServer.Data package.
- See also: Resolve NuGet dependency conflicts.
The following sections show package families as they are named in the release notes and bug list, with the packages that belong to each family.
EPiServer.CMS.Core
These packages are for Optimizely Content Management System (CMS). The EPiServer.CMS.Core package acts as an umbrella package and depends on the individual CMS assembly packages listed below.
- EPiServer.CMS.AspNetCore
- EPiServer.CMS.AspNetCore.HtmlHelpers
- EPiServer.CMS.AspNetCore.Mvc
- EPiServer.CMS.AspNetCore.Routing
- EPiServer.CMS.AspNetCore.TagHelpers
- EPiServer.CMS.AspNetCore.Templating
- EPiServer.CMS.Core
- EPiServer.Framework
- EPiServer.Framework.AspNetCore
- EPiServer.Hosting
EPiServer.CMS.UI
These packages are for Optimizely Content Management System (CMS).
- EPiServer.CMS.UI
- EPiServer.CMS.UI.Admin
- EPiServer.CMS.UI.AspNetIdentity
- EPiServer.CMS.UI.Core
- EPiServer.CMS.UI.Settings
- EPiServer.CMS.UI.Sources
- EPiServer.CMS.UI.VisitorGroups
- EPiServer.CMS.UI.ContentManager
Optimizely.Graph.Cms
These packages are for integration with Optimizely Graph.
- Optimizely.Graph.Cms
- Optimizely.Graph.Core
- Optimizely.Graph.Query
- Optimizely.Graph.AspNetCore
📘 Note EPiServer.Find packages are not compatible with CMS 13. Use Optimizely Graph or other supported search solutions when building CMS 13 applications.
Optimizely.CMS
These packages are for Optimizely CMS management API.
- Optimizely.Cms.Contracts.V1
- Optimizely.Cms.Service.V1
- Optimizely.Cms.Service.V1.Authentication
- Optimizely.Cms.Service.V1.Authentication.Configuration
- Optimizely.Cms.Service.V1.Content
- Optimizely.Cms.Service.V1.Core
- Optimizely.Cms.Service.V1.Packaging
- Optimizely.Cms.Service.V1.Security
- Optimizely.Cms.Service.V1.Webhooks
- Optimizely.Cms.Webhooks.V1
- Optimizely.Cms.Webhooks.V1.EventProcessors
EPiServer.Commerce
These packages are for Optimizely Commerce Connect.
- EPiServer.Commerce
- EPiServer.Commerce.Core
- EPiServer.Commerce.UI
- EPiServer.Commerce.UI.Admin
- EPiServer.Commerce.UI.CustomerService
- EPiServer.Personaliztion.Commerce (This is listed under EPiServer.Commerce release but follows a separate major version cadence.)
- EPiServer.Tracking.Commerce (This is listed under EPiServer.Commerce release but follows a separate major version cadence.)
EPiServer.ContentDeliveryApi and EPiServer.ContentManagementApi
These packages are for the Optimizely Content Management System (CMS) application programming interface (API).
📘 Note The EPiServer.ContentDeliveryApi and EPiServer.ContentManagementApi packages are compatible with CMS 13 and maintain feature parity with CMS 12. They do not support CMS 13 features.
- EPiServer.ContentDeliveryApi.Cms
- EPiServer.ContentDeliveryApi.Commerce
- EPiServer.ContentDeliveryApi.Core
- EPiServer.ContentDeliveryApi.Forms
- EPiServer.ContentDeliveryApi.Search
- EPiServer.ContentDeliveryApi.Search.Commerce
- EPiServer.ContentManagementApi