World is now on Opti ID! Learn more

smithsson68@gmail.com
Dec 19, 2008
  17374
(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
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |