Take the community feedback survey now.

smithsson68@gmail.com
Dec 19, 2008
  17385
(0 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
A day in the life of an Optimizely OMVP - Opticon London 2025

This installment of a day in the life of an Optimizely OMVP gives an in-depth coverage of my trip down to London to attend Opticon London 2025 held...

Graham Carr | Oct 2, 2025

Optimizely Web Experimentation Using Real-Time Segments: A Step-by-Step Guide

  Introduction Personalization has become de facto standard for any digital channel to improve the user's engagement KPI’s.  Personalization uses...

Ratish | Oct 1, 2025 |

Trigger DXP Warmup Locally to Catch Bugs & Performance Issues Early

Here’s our documentation on warmup in DXP : 🔗 https://docs.developers.optimizely.com/digital-experience-platform/docs/warming-up-sites What I didn...

dada | Sep 29, 2025

Creating Opal Tools for Stott Robots Handler

This summer, the Netcel Development team and I took part in Optimizely’s Opal Hackathon. The challenge from Optimizely was to extend Opal’s abiliti...

Mark Stott | Sep 28, 2025

Integrating Commerce Search v3 (Vertex AI) with Optimizely Configured Commerce

Introduction This blog provides a technical guide for integrating Commerce Search v3, which leverages Google Cloud's Vertex AI Search, into an...

Vaibhav | Sep 27, 2025

A day in the life of an Optimizely MVP - Opti Graph Extensions add-on v1.0.0 released

I am pleased to announce that the official v1.0.0 of the Opti Graph Extensions add-on has now been released and is generally available. Refer to my...

Graham Carr | Sep 25, 2025