Updating DynamicWeb 10
How to update DynamicWeb 10
To update to the latest Dynamicweb version, you need to load the latest application - either using nuget, docker or a zipped download.
To update a project using nuget, use dotnet add package command
Updating Dynamicweb.Suite
$ dotnet add package Dynamicweb.Suite
Updating Dynamicweb.CMS
$ dotnet add package Dynamicweb.Cms
Customizations reside in the Files archive in /Files/System/AddIns and will be picked up by Dynamicweb and the customizations needs no updates or changes to update Dynamicweb. The Dynamicweb API is compatible within major version.
DynamicWeb Cloud
Solutions hosted by DynamicWeb will follow a version-less deployment strategy. It will no longer be possible to remain on updated versions og the application. New versions are released using a Milestone cadence running for a Month. This means that new features are released as soon as possible after they are completed.
Milestones
Milestone releases follow a first-in-first-out principle. Think a numbered list where the newest element in the list is added to the beginning and the last element is removed.
The current milestone will contain the latest features and functionality, and will continue to receive bugfixes on a daily basis.
The previous milestone will only receive critical bugfixes weekly if applicable. This release can be considered semi-stable.
The next two milestones will not receive bugfixes, and will not change. These releases can be considered stable.
In addition to the milestone releases, it will also be possible to use a nightly release that is updated every night. The nightly release contains a snapshot of the current development branch. This means it's not guaranteed to be stable in any way, and there's no support when using this version.
Warning
It is not recommended to use the nightly release for anything other than testing
Inside DynamicWeb Administration, there will be a setting to choose which milestone tier to lock the solution to, e.g., Current + 2. This means that the solution will always run on the milestone in position 3 in the illustration below. When a new milestone is released, the one from position 2 moves to position 3, which means that the solution locked to Current + 2 will be updated to the version that was Current + 1.
| 1 | 2 | 3 | 4 |
|---|---|---|---|
| Current | Current + 1 | Current + 2 | Current + 3 |
Examples
This example shows the release milestones at the time when Milestone 5 is released.
| 1 | 2 | 3 | 4 |
|---|---|---|---|
| M5 | M4 | M3 | M2 |
This example shows the release milestones at the time when Milestone 8 is released.
| 1 | 2 | 3 | 4 |
|---|---|---|---|
| M8 | M7 | M6 | M5 |
Self-hosted
When hosting DynamicWeb 10 outside the DynamicWeb Cloud, there are more options for how to handle updating the application. While the milestone releases are not available as specifically named packages, they follow the version paradigms defined by the various delivery mechanisms.
Docker
Running DynamicWeb on Docker makes the update very easy. If a Docker image is referenced by a tag rather than a sematic version, then simply pull the new version of the image and start the container again.
NuGet / Project Templates
If the solution was created from our project templates, they already reference the very latest NuGet packages. This can be changed to be as specific or as unspecified as necessary. If an unspecified version pattern is used, NuGet will pull the latest package matching the pattern when a restore is run. Using these non-specific versions allow for easy update of custom solutions using NuGet.
To update a project based solution, restore nuget packages
$ dotnet restore