That's great!
Thank you very much for this.

For WinSCP scripting, you just need winscp.com and winscp.exe. No other files.

See also https://winscp.net/eng/docs/executables

"keep own copy of the binaries" - it is a great idea, but what exactly would that mean?

Is WinSCPnet.dll needed too and what about the other subdirectories that contain "Extensions" and "PuTTY". I would never need the GUI version, of course (that would be winscp.exe ?), but what would I need of all the installation in order to ensure that winscp.com works for my automation? Are there any registry entries that the winscp.com operation is dependent on?

Tedy wrote:

As I have already deployed WinSCP, I have found that removing the "Translations" folder from the WinSCP installation meant that the WinSCP output was always in English irrelevant of the Windows language.

I would not rely on the installed copy of WinSCP. For automation, it is better have your own copy of the binaries, so that your application does not break when someone re-installs WinSCP.

Would interpreting the XML log files (as opposed to interpreting the WinSCP output) result in any performance advantage at all?

No.

Hi Martin,

Thank you very much for this very helpfull quick reply.
I could not find all these details in the online documentation.

I have already interpreted the WinSCP output in my application and so the best solution for me was to use the "raw configuration setting".
As I have already deployed WinSCP, I have found that removing the "Translations" folder from the WinSCP installation meant that the WinSCP output was always in English irrelevant of the Windows language.

I do not have the .NET development tools; I use an old version of MS Studio (2015) C++ and so am unable to use the WinSCP .NET assembly.

Would interpreting the XML log files (as opposed to interpreting the WinSCP output) result in any performance advantage at all?

First, do not interpret WinSCP output.
Interpret XML log file
https://winscp.net/eng/docs/logging_xml
Or even better, use WinSCP .NET assembly:
https://winscp.net/eng/docs/library

Anyway, if you do not want WinSCP to use localizations, do not deploy them. If you deploy only winscp.exe and winscp.com, with no locations files, WinSCP will always run in English.

You can also use raw configuration setting:
https://winscp.net/eng/docs/rawconfig#localesafe

When runing scripts using winscp.com communicating with a server the results are stored in text files. These contain text in the language that is set as the default for Windows. This means that an application that has to interpret these files has to be multi-lingual in order to support Windows in different languages.

For example: if the application that interprets the winscp.com text files expects English text like "No files found" and Windows uses French as its default language therefeore the text would be "Aucun fichier ..." the application will not interpret correctly the winscp.com text files.

My question:
Is there any chance that the resulting files created by winscp.com would always use English, no matter what the Windows default language is?

Thank you for your great software and for your support.