Differences
This shows you the differences between the selected revisions of the page.
| 2025-01-26 | 2025-01-26 | ||
| no summary (174.229.180.93) (hidden) (untrusted) | no summary (174.229.180.93) (hidden) (untrusted) | ||
| Line 40: | Line 40: | ||
| - | ===== [[configuration]] Sharing Configuration with Graphical Mode ===== | ||
| - | In scripting/console mode, WinSCP shares [[config|configuration]] with [[interfaces|graphical mode]] by default. While this can be useful in some cases, it can also be a disadvantage. | ||
| - | The disadvantage is that change to configuration in graphical mode may break your script (common example is enabling //[[ui_synchronize|Existing files only]]// option for [[task_synchronize_full|synchronization]]). Also the script is not portable to other machines, when it relies on an external configuration. | ||
| - | |||
| - | If you want to protect your script from such inadvertent change or if you want to make the script portable, you should isolate its configuration from graphical mode explicitly. | ||
| - | |||
| - | The best way to do that is to configure all the options you need using script commands only (''[[scriptcommand_option|option]]'' command, switches of other commands, [[session_url|session URL]]), or if no such command is available, using [[rawsettings|raw site settings]] and [[rawconfig|raw configuration]]. Finally force scripting mode to [[config#no|start with the default configuration]] using ''[[commandline#configuration|/ini=nul]]'' command-line parameter. | ||
| - | |||
| - | Alternatively [[config#export|export your configuration]] to a separate INI file and reference it using ''[[commandline#configuration|/ini=]]'' command-line parameter. Also consider setting the INI file read-only, to prevent WinSCP writing to it, when exiting. Particularly, if you are running multiple scripts in parallel, to prevent different instances of WinSCP trying to write it at the same time. | ||
| ===== Generating Script ===== | ===== Generating Script ===== | ||