Top

On-Premise Installation: installers post 6.10.0

 

Overview

Starting after ConceptShare 6.10.0, installers will no longer be additive/sequential in their operation. This is in contrast to the workings of previous installers (please see Background section). After updating to 6.10, when you apply the installer file, you will be updated directly to that version. This new approach will save time for on-premise IT teams by requiring downloads of (approximately 90%) smaller installer files, and by turning a series of sequential, gated updates, into a single update.

 

Important note to on-premise administrators

If you are currently running a version older than 6.10.0 , you must first perform an update to 6.10.0 explicitly. That installer performs background actions and is the bridge between the old and the new installer formats. Without first upgrading to 6.10.0 explicitly, this “bridge” data will not be available to later installer files, and therefore, they cannot update your instance correctly.

You can download the 6.10.0 Installer here:

 

After successfully installing 6.10.0, please ensure the follow two edits are made to your ConceptShare web.config file.

1. Ensure the following is added to the web.config under the system.webServer node:

<modules>
  <remove name="TelemetryCorrelationHttpModule" />
  <add name="TelemetryCorrelationHttpModule" type="Microsoft.AspNet.TelemetryCorrelation.TelemetryCorrelationHttpModule, Microsoft.AspNet.TelemetryCorrelation" preCondition="integratedMode,managedHandler" />
  <remove name="ApplicationInsightsWebTracking" />
  <add name="ApplicationInsightsWebTracking" type="Microsoft.ApplicationInsights.Web.ApplicationInsightsHttpModule, Microsoft.AI.Web" preCondition="managedHandler" />
</modules>

2. Ensure the following is added to the web.config under the runtime\assemblyBinding node:

<dependentAssembly>
    <assemblyIdentity name="Microsoft.ApplicationInsights" publicKeyToken="31bf3856ad364e35" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-2.4.0.0" newVersion="2.4.0.0" />
</dependentAssembly>
<dependentAssembly>
    <assemblyIdentity name="Microsoft.Azure.KeyVault.Core" publicKeyToken="31bf3856ad364e35" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-2.0.0.0" newVersion="2.0.0.0" />
</dependentAssembly>
<dependentAssembly>
    <assemblyIdentity name="System.IO.Compression" publicKeyToken="b77a5c561934e089" culture="neutral" />
    <bindingRedirect oldVersion="0.0.0.0-4.1.2.0" newVersion="4.1.2.0" />
</dependentAssembly>

 

Background

Historically, ConceptShare's on-premise installers (v 4.0.0 - v 6.10.0) have been sequential and cumulative.

Ex. suppose you are on version A and want to upgrade to version X using the old installers: You would download the version X installer, which would upgrade your installation by sequentially applying upgrades B, then C, all the way through X.

Each installer file contained the entire chronological history of updates. This approach allowed an administrator to stop the update at any intermediate version; however, it imposed a burden on administrators too, forcing them to sit through intermediary updates in order to get to the end-point they actually wanted. Additionally, this approach made each subsequent installer file grow in size relative to its predecessor. At the time of writing, the older installer files had grown to 4GB in size, while the newer installers are closer to 400MB each.

 

 

Was this article helpful?
0 out of 0 found this helpful