smithsson68@gmail.com
Dec 19, 2008
  19046
(2 votes)

Installer changes in new EPiServer Relate+ package

The much awaited EPiServer Relate+ package was released yesterday, you can find more details here.

With Relate+ comes a new version of the installation system that was first released with CMS 5 R2. In this version we have taken the opportunity to move most of the code into a new common library (EPiServerInstall.Common.1.dll) as we found, not surprisingly, that almost everything we had done for CMS 5 R2 was reusable for the Relate+ and Community packages. This does of course mean many breaking changes but we took this decision based on the fact that not many partner developers have started using the installer Cmdlets and API's yet (apologies if you have).

The release includes many bug fixes including better UI validation, real-time execution of Cmdlets (see this blog entry for more details) and probably the most obvious is that the EPiServer Installation Manager has been renamed to EPiServer Deployment Center.

The are 2 main reasons for this:

  1. Program links added to the Windows Start Menu containing the words 'install', 'uninstall' or 'setup' are not highlighted as they should be. This is for security reasons.
  2. Once we started thinking about changing the name we all agreed that what this application actually does is deploy stuff rather than install it. You will still see the words install and uninstall used in the application but we felt they were still appropriate in their context.

It's worth noting that the actual EPiServer Deployment Center exe file is still called EPiServerInstall.exe. This is for backward compatibility reasons.

A new version of Fredrik Tjärnberg's Power Tools that works with the new API's will be released in due course.

Whilst we appreciate that the installation and deployment of EPiServer products is merely a "starter" to the main course, we naturally want to make sure that it works well, so your feedback is welcome.

Dec 19, 2008

Comments

Please login to comment.
Latest blogs
Four database surprises when upgrading from CMS 11 to CMS 13

We're in the middle of migrating a fairly large site from CMS 11 / .NET Framework to CMS 13 / .NET 10. The code migration is one thing, but the...

Per Nergård (MVP) | Jun 12, 2026

Designing ODP Real-Time Audiences for CMS Personalization and Experimentation

A practical look at when to use ODP Real-Time Audiences, how to build them, and how they fit into CMS personalization and Feature Experimentation.

Wojciech Seweryn | Jun 11, 2026 |

Unlock Experimentation with Content Variations in CMS 13

Part 1 argued that Content Variations is the CMS 13 feature that didn't get the keynote but should have. This is the follow-up: wiring those...

Piotr | Jun 11, 2026

umage.ai is now an Optimizely Silver Solution Partner

umage.ai is officially an Optimizely Silver Solution Partner. The badge formalises an alignment that was already there — agent-driven Optimizely wo...

Allan Thraen | Jun 10, 2026 |