Just as the EPiServer CMS version numbers are a bit tough to remember, the corresponding database versions are even worse. Typically you don’t really need to bother, since this stuff is taken care of by the Deployment Center. But if something goes wrong you may need to apply database upgrade scripts by hand, and then you really need to know the correct numbers.
Do you often wake up in the middle of the night, wondering about the assembly version number of a specific EPiServer CMS release? Then this reference list is for you.
Just a quick heads-up that EPiServer 6 was released today. Among the improvements is the awaited support for TinyMCE. Good job guys and all that, but please, why market the brand new product with this single screenshot:
The EPiServer Awards nominees got in today. 22 sites were selected from the 118 contributions and I’m proud to see NetRelations featured in the list with the cool intranet we built for Swedish fashion chain MQ.
One of the new features in EPiServer R2 version is the relocation of system folders. In previous versions they were stored in the same folder as the other site related files, but now they seem to be installed in Program Files by the new Installation Manager. I fail to see the benefits of this. For safety and security reasons, deployers seldom have complete access to areas such as Program Files.
The very popular content management system EPiServer is about to get a major upgrade to version 5. For some reason the name has been chosen as “EPiServer CMS”, but at least it’s better than “EPiServer 2007” or “EPiServer Ultimate”.
The first release candidate version was released during spring and I’ve been working a lot with the RC3 version during the summer. Last week, the RC4 version of EPiServer CMS was released and it might actually be the final release if we’re lucky.
