I'm using WinSCP to upload files to a server using script, since I store files list in MS SQL database, I tried to create a script for WinSCP from SQL Stored procedure by concatenating strings and saving results to file using SQL CLR assembly, but it seems there's a problem with newline characters - in SQL i use CHAR(13) + CHAR(10) and when i'm trying to connect to server using WinSCP i've got error:
"Ambiguous command 'o'. Possible matches are: open, option".
But when I edit this script manually in notepad.exe, even if i don't edit a single character and save it, it works. How should i properly handle newline characters for WinSCP?
Or is there a way to change accepted encoding of scripts in WinSCP? I googled about encoding settings in WinSCP but if i understand correctly, you can change encoding of files transferred using WinSCP, not encoding of the WinSCP script.