EPiServer update 67
This update includes a couple of new features for CMS Core regarding Visual Studio integration and support for installing database schema in manually created databases. The release also includes support for automatic database upgrades for Commerce and it contains bug fixes for Commerce and Find. Read more on the automatic database upgrades and Visual Studio integration in Per Bjurström's blog post: Automatic database updates, Visual Studio 2015 and MVC 5.
The update is applicable to EPiServer projects version 7.5 and higher, and contains finalized work items included in the latest iteration. The update is available for installation from the EPiServer NuGet feed. Continuous release updates are cumulative, meaning that the latest always includes previous updates. All platform updates are supported and we strongly recommend that you keep ongoing projects up to date.
Latest changes
Click a package in the list below to see work item details. Refer to Release notes for an overview of latest changes. See Installing EPiServer updates for information on how to install EPiServer updates using NuGet.
Updated packages
EPiServer Core
Features
- #126190 New projects in Visual Studio should be based on MVC 5
When creating new projects in the Visual Studio extension they should be based on MVC 5. - #114358 Support for installing database schema in manually created database
See About the database for more information. - #125875 SEO: Use alternative URLs in Alloy sample package
The Alloy site template has been updated to use alternative URLs. - #118378 Support for Visual Studio 2015 in Visual Studio extension
The CMS Visual Studio extension now works in Visual Studio 2015.
EPiServer Commerce
- EPiServer.Commerce 8.13.0
- EPiServer.Commerce.Core 8.13.0
- EPiServer.Commerce.UI 8.13.0
- EPiServer.CommerceManager 8.13.0
Features
- #115577 Support for automatic database upgrades in continuous deployment.
Refer to Automatic schema updates and Updating configuration and database schemas.
EPiServer Find
- EPiServer.Find 9.3.1 (only back-end fixes, no package download)
Issues with NuGet updates
In some specific upgrading scenarios you might experience problems with the dependency chains, due to issues in NuGet. This mostly affects Commerce and Find, but might also occur when updating CMS. The workaround is usually to update the packages one-by-one. Refer to Issues with NuGet package updates for more information.
Important notifications
Note the following version-specific information:
- From update 66, EPiServer Commerce only features that are Azure Database compliant will be available by default, non-compliant features have to be manually configured.
- Update 55 included breaking changes for CMS and Find.
- From update 40, workflows are disabled by default to simplify Azure deployment. Refer to Activating workflows for information on how to enable them.
- Update 36 included breaking changes for Commerce, refer to Breaking changes Commerce 8.
- From update 35, .NET Framework 4.5 is required, see System requirements and Upgrading to .NET Framework 4.5.
- From update 6, EPiServer UI components (CMS and Commerce after version 7.6.0) have been converted to NuGet packages. Location of packages have changed and might affect the installation if you are going from the first to the latest update, refer to Changes to package locations.
Related information
- Installing EPiServer updates – adding the NuGet feed and installing EPiServer updates to existing solutions.
- About the EPiServer continuous release process – deployment options with the EPiServer continuous releases.
Last updated: Jun 01, 2015
