Migrating Go Current to Update Service
The Go Current application has been renamed to Update Service in the latest version. The updated version of the application utilizes a modern .NET architecture, specifically ASP.NET Core, making it more future-proof and SaaS-ready.
The following lists the breaking changes going from Go Current to Update Service and the steps needed to migrate.
Server
We have rebuilt the server from scratch and now it's hosted on IIS, replacing the previous Windows service. Additionally, the communication between the server and the client has changed. Consequently, the old Go Current server cannot be upgraded directly to the new Update Service.
However, we have developed a migration process that enables you to maintain your current setup. This involves installing the Update Service server with the same database as the Go Current server and migrating clients deployed in the field to the new one.
See the server migration page for further information.
Server Cmdlets
The server cmdlets have been updated with a new prefix, -Uss, which replaces -Gocs. In addition, a few cmdlets and parameters have been renamed to enhance consistency with the REST API.
See the server cmdlets migration page for further information.
Client
The latest client version is equipped to communicate with both the old Go Current server and the new Update Service server. To update your clients to the latest version and migrate to the new Update Service server, follow the steps outlined on the server migration page.
Client Cmdlets
The client cmdlets have been updated with a new prefix, -Usc, which replaces -Goc. In addition, a few cmdlets and parameters have been renamed to enhance consistency with the REST API.
See the client cmdlets migration page for further information.
LS Retail's servers
A new server is now available for the Update Service to retrieve packages from: https://updateservice.lsretail.com. The old server for Go Current, gocurrent.lsretail.com, will remain operational until at least March 1, 2024.