The release of EPiServer CMS 6 is just around the corner and there are several frequently asked questions concerning everything from system requirements to new functionality for web editors. This article aims at answering some of those questions. Further articles will be published outlining new and enhanced functionality in EPiServer CMS 6.
No. EPiServer CMS 4 sites must first be migrated to EPiServer CMS 5, from where they can be upgraded to EPiServer CMS 6.
No. The XForms data is migrated automatically to the new Dynamic Data Store during the installation process, but otherwise the upgrade script takes care of the entire upgrade.
EPiServer CMS 6 will have official support for Microsoft Windows Server 2003 and 2008, both 32 and 64 bit. We do however recommend Microsoft Windows Server 2008 R2 64 bit. Please see the system requirements for further information.
Of course you can. EPiServer CMS 6 RC1 has been tested, but we do at this point guarantee 100% watertight development. Versions 5 and 6 are very similar, so changing to version 6 late on in the project should be relatively easy, without risking too many problems.
If you are interested in making use of the new technology in version 6, like Dynamic Data Store or gadgets, you can build these parts in RC1 and then later migrate them into the main project. Please also note that the APIs may be changed in the final release.
Technically yes, although this is not a general recommendation as we recommend Microsoft Windows Server 2008 R2 64 bit.
EPiServer CMS 4 and 6 sites will not be able to be run with the same license key. A new license key will be required for EPiServer CMS 6.
Performance in EPiServer CMS 6 has been greatly improved due to the mirroring improvements and dynamic data store functionality.
We have upgraded EPiServer World to EPiServer CMS 6 without any problem and know that several other websites also plan to upgrade within the near future.