Proper Update Method for Windows

[pavichokche]

I'm running the client as a service on Windows. Every time I update I shut it down, back up the program directory, and then extract the new release zip file EXCEPT the web.config and appsettings.* files. Is that correct? Is there a proper update methodology for Windows?

[mtechnomaniac]

I'm running the client as a service on Windows. Every time I update I shut it down, back up the program directory, and then extract the new release zip file EXCEPT the web.config and appsettings.* files. Is that correct? Is there a proper update methodology for Windows?

I'm also looking for the right instructions to update. please confirm if this is the best way to do it

[mtechnomaniac]

I'm running the client as a service on Windows. Every time I update I shut it down, back up the program directory, and then extract the new release zip file EXCEPT the web.config and appsettings.* files. Is that correct? Is there a proper update methodology for Windows?

I'm not sure if you found the correct solution yet but here's what I did instead of manually downloading the udpate:

1. Open 'Windows Powershell' with admin
2. Navigate to the folder where RDT client is installed
3. Type the following command (without quotes) for autoupdate: ".\update.ps1"

I initially got the following error: "ps1 cannot be loaded because running scripts is disabled on this system. For more information, see about_Execution_Policies at https:/go.microsoft.com/fwlink/?LinkID=135170"
Used this command to enable scripts in PowerShell: "Set-ExecutionPolicy -ExecutionPolicy Unrestricted"
You can confirm if the policy is enabled using: "Get-ExecutionPolicy"
Output should be "Unrestricted"
Additionally I disabled 'running scripts' using the following command (of course after the update completed sucessfully): "Set-ExecutionPolicy -ExecutionPolicy Restricted"

P.S: There is no need to backup files before updating RDT Client but I did it nevertheless and made a copy of the entire folder (old version), in case something goes wrong and I needed a fallback

[medinauta]

There's a file called How to update in the root folder where you need to open a power shell with admin rights and run ".\update.ps1". Unfortunately for me it didn't work. After downloading and extracting the files I got an error that it couldn't replace a directory that already existed (the root). After a little reading, I just gave up and did it manually, extracted the zip and replace files. The most important files are the appsettings and the database (which is unaffected for the files replacement).

[mtechnomaniac]

We are trying to update on Windows and can't find any 'How to Update' file in root folder. There's only that 'update.ps1', at least in versions 2.0.81 & above

[pavichokche]

The most important files are the appsettings and the database (which is unaffected for the files replacement).

The release .zip being distributed DOES contain an appsettings.json file, so our most important files would be affected by doing a straight-forward file replacement...