RoyMill wrote:

Command are documented here: https://winscp.net/eng/docs/scriptcommand_option

Thanks for noticing. I have removed this from the documentation.

I understand the -transfer=ascii and -transfer=binary switches on the put and get is the best way to go, but wanted to just use the aliases ascii and binary since my folks are familiar with those commands. Does anybody see this being a problem in the future?

Also, is it acceptable to use the alias dir instead of the ls command to list a remote directory?

While we have no plans to remove these aliases any time soon, I would definitely recommend you to use supported syntax only.

Hello,

We are converting our FTP scripts to WinSCP and would like to keep the script commands close to what we are currently using. We will be using FTP and FTP with TLS explicit encryption.

We use the commands ascii and binary on our current product and wondered if we could use the commands option transfer ascii and option transfer binary or preferably their aliases ascii and binary in WinSCP. I saw where these commands are deprecated so didn't want my folks to use them and then have them removed in a later release.

Command are documented here: https://winscp.net/eng/docs/scriptcommand_option

But show deprecated here: https://winscp.net/eng/docs/guide_ftp_script_to_sftp

I understand the -transfer=ascii and -transfer=binary switches on the put and get is the best way to go, but wanted to just use the aliases ascii and binary since my folks are familiar with those commands. Does anybody see this being a problem in the future?

Also, is it acceptable to use the alias dir instead of the ls command to list a remote directory?

Thank you very much.