Package Management

From Dynamicweb 9.2 and up, you have access to the Dynamicweb package manager – a more flexible way of downloading and installing updates on your Dynamicweb solution.

This means that a lot of the time you no longer have to wait for a major or service release before you can fix a particular problem – as soon as a fix is ready on our end it will be released, which will make it available for download immediately.

This document describes how to use the package manager.

Requirements

The following requirements apply:

  • Package management is not available for solutions on Free/Express or Professional licenses.
  • Your solution needs to be set up as a custom solution (it needs its own application folder).
  • The application pool needs to have Load User Profile activated. Contact Servicedesk if your solution needs to be converted to custom.

If your installation follows the Dynamicweb guidelines you will need to set up a packages root folder with a short path (this is due to limitations in Microsoft IIS).

  • Go to Settings -> Packages -> Package configuration
  • Enter a short root path, e.g E:\InstalledPackages
Figure 2.1 Creating a short path to get around potential IIS problems

On a shared environment?

If you are on a shared hosting environment, please contact Servicedesk before updating any packages!

To view a list of the package updates available at any point:

  • Go to Settings -> Packages -> Updates
  • Browse the list of available package updates (Figure 3.1)
Figure 3.1 The list of updates available for download
  • Select one to view details on package contents and any release notes (Figure 3.2)
  • If this is the first time you’re updating packages you will be informed that you need to restore missing packages first - click Restore to do so.
  • After restoring missing packages click Update to update your package and finish the process
Figure 3.2 Viewing package details - the Restore packages notice has been highlighted

You will be logged out when the package has been updated – this is because an update forces a pool recycle.