Skip to main content
Version: v2.6

Deployment Notes 2.6.13

Introduction​

Artifacts can be downloaded from the download page.

The following sections outline the deployment actions for this release.

Database Migration​

Important

Please back up all databases before running refactor scripts

Redeploy Portal​

  1. Download the appropriate zip file from the download page depending on your installation
    1. If you are using the Portal including all modules (Item Manager and Planning), download portalwithmodules.zip
    2. Otherwise, download portal.zip and - if relevant - ext-itemmgr.zip or ext-planning.zip
  2. Redeploy the Portal web application.
    1. Preserve and re-establish the appsettings.json file
    2. If you are hosting the Portal in an IIS sub-folder, you should also preserve and re-establish the <base> tag in the wwwroot/index.html file

If you are selectively deploying the Item Manager or Planning modules, you need to copy the contents of the Server and Client folders from the zip file to their respective locations in the Extensions folder under the Portal application folder

Upload new runtime to the Portal​

  1. Download the runtime.zip from the download page
  2. Upload new runtime.zip to the Portal (Configuration → Operations → Runtime → Upload)
  3. Set the new runtime version active

Workstations​

Reinstall Visual Studio Extension​

  1. Make sure you have at least Visual Studio 2022 version 17.4 installed
  2. Open Visual Studio and in Extensions → Manage Extensions, mark the installed Hopp Migration extension for un-install
  3. Close Visual Studio. The Microsoft Visual Studio extension installer will launch to uninstall the previous version. Follow the guidance in the installer
  4. Install the Hopp Visual Studio extension (double-click VsExtension.2022.vsix)
  5. Follow the guidance in the installer

Powershell Automation​

Re-install the PowerShell Automation module on relevant workstations and servers.

note

This is optional and only if the Powershell Automation scripts are used

Check custom Portal extensions before upgrading​

An endpoint with no [Authorize], [AllowAnonymous] or [AuthorizeUrl] attribute now answers 401 to callers who are not signed in.

  1. Review the endpoints in any custom Portal extension
  2. Mark the ones that must stay public with [AllowAnonymous]
  3. Rebuild the extension and redeploy it together with the Portal

The new behavior cannot be switched off by configuration.

If you want to keep download links out of the Portal log, add the Override block to the appsettings.json you preserve when redeploying the Portal:

"Serilog": {
  "MinimumLevel": {
    "Default": "Information",
    "Override": {
      "Microsoft.AspNetCore.Hosting.Diagnostics": "Warning"
    }
  }
}

Leave the rest of the Serilog section as it is.