Skip to main content
All CollectionsAnnouncementsAnnouncements and archive
Breaking change: replacing scriptcs with dotnet-script for Workspace 365 install packages
Breaking change: replacing scriptcs with dotnet-script for Workspace 365 install packages

Breaking change

Updated over 5 months ago

Hi,

The Workspace 365 update process currently uses PowerShell and scriptcs to deploy our software. Since the scriptcs project is no longer maintained we are working on migrating our deployment process over to dotnet-script.

To further simplify our deployment process, we have decided to replace the PowerShell scripts with dotnet-script as well. This way there is a single scripting language (and dependency) for the entire deployment process.

Deploying Workspace 365 with dotnet-script changes the requirements for the servers used to host our services. The additional requirement will be to install the latest version of the .Net 8.0 SDK on all servers running our software. If you want to prepare your servers before the upgrade to minimize the work outside of working hours, we advise you to schedule the installation beforehand.

This will not impact any running services.

This change will become effective starting with the release of Workspace 365 v4.13. Further instructions will be provided in the download article for Workspace 365 v4.13, as these require the files provided in the update package. This will become available on Tuesday August 13th.

Did this answer your question?