smithsson68@gmail.com
Dec 19, 2008
  18994
(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
Announcing new library: SettingsManager

When you run .net app, there have been a few ways to store settings. Those can be set via appSettings.json, or via Azure Portal AppService...

Quan Mai | Apr 30, 2026

From Prompting to Production: Optimizely Opal University Cohort and the Future of Agentic MarTech

Most organizations today are still playing with AI. They experiment with prompts, test ideas in isolated chats, and occasionally automate a task or...

Augusto Davalos | Apr 28, 2026

Six Compelling Reasons for Upgrading to CMS 13

Most software updates ask you to keep up. Optimizely CMS 13 asks something different — it asks whether your digital strategy is built for a world...

Muhammad Talha | Apr 28, 2026

Optimizely CMS 13 breaking changes: GetContentTypePropertyDisplayName

When upgrading from CMS 12 to 13, resolving property display names may not work as before. Here’s what changed.

Tomas Hensrud Gulla | Apr 27, 2026 |

Accelerate Optimizely DAM Adoption: Unlocking Business Value with Metadata Bulk Import

Accelerating Optimizely DAM Adoption How a Metadata-Driven Bulk Import Utility Unlocks Real Business Value Executive Summary For enterprises runnin...

Vaibhav | Apr 27, 2026

Optimizely CMS 13 breaking changes: IValidate<T>

Custom IValidate validators in Optimizely CMS 13 are no longer auto-discovered. They must be registered explicitly when upgrading from CMS 12.

Tomas Hensrud Gulla | Apr 27, 2026 |