guide_schedule » Revisions »

Differences

This shows you the differences between the selected revisions of the page.

2015-12-17		2015-12-23
removing uses of option batch and confirm not needed since 5.6 with release of the next major branch 5.8 (martin)		5.8 Script or .NET assembly code template can be generated in GUI. (martin)
	Line 24:		Line 24:
	* In //Add arguments// add appropriate WinSCP [[commandline\|command-line]] parameters to execute the [[scripting#commands\|scripting commands]] you need (typically you will use ''/script'' or ''/command'' parameters).		* In //Add arguments// add appropriate WinSCP [[commandline\|command-line]] parameters to execute the [[scripting#commands\|scripting commands]] you need (typically you will use ''/script'' or ''/command'' parameters).
	* You should also add ''/log'' parameter to turn on [[logging\|session logging to file]].		* You should also add ''/log'' parameter to turn on [[logging\|session logging to file]].
-	* The resulting arguments may look like: \\ ''%%/log=c:\path\winscp.log /command "open sftp://user:password@example.com/" "put d:\examplefile.txt /home/user/" "exit"%%'' \\ Note that the command-line parameter ''/console'' was not specified, what makes ''WinSCP.exe'' not show the console window, not to disturb you while you are using your workstation.	+	* The resulting arguments may look like: \\ ''%%/log=c:\path\winscp.log /command "open sftp://user:password@example.com/" "put d:\examplefile.txt /home/user/" "exit"%%'' \\ Note that the command-line parameter ''/console'' was not specified, what makes ''WinSCP.exe'' not show the console window, not to disturb you while you are using your workstation. \\ You can have WinSCP [[ui_generateurl\|generate the command-line template]] for you.
	* If your script uses local paths relative to the script path or WinSCP executable path, specify the respective path in //Start in// field.		* If your script uses local paths relative to the script path or WinSCP executable path, specify the respective path in //Start in// field.
	* When done, click //Next//, review your options and confirm with //Finish//.		* When done, click //Next//, review your options and confirm with //Finish//.
	Line 34:		Line 34:
	* In advanced properties add appropriate WinSCP [[commandline\|command-line]] parameters to execute the [[scripting#commands\|scripting commands]] you need (typically you will use ''/script'' or ''/command'' parameters).		* In advanced properties add appropriate WinSCP [[commandline\|command-line]] parameters to execute the [[scripting#commands\|scripting commands]] you need (typically you will use ''/script'' or ''/command'' parameters).
	* You should also add ''/log'' parameter to turn on [[logging\|session logging to file]].		* You should also add ''/log'' parameter to turn on [[logging\|session logging to file]].
-	* The resulting command may look like: \\ ''%%"C:\Program Files (x86)\WinSCP\WinSCP.exe" /log=c:\path\winscp.log /command "open sftp://user:password@example.com/" "put d:\examplefile.txt /home/user/" "exit"%%'' &winpath &win64 \\ Note that the command-line parameter ''/console'' was not specified, what makes ''WinSCP.exe'' not show the console window, not to disturb you while you are using your workstation.	+	* The resulting command may look like: \\ ''%%"C:\Program Files (x86)\WinSCP\WinSCP.exe" /log=c:\path\winscp.log /command "open sftp://user:password@example.com/" "put d:\examplefile.txt /home/user/" "exit"%%'' &winpath &win64 \\ Note that the command-line parameter ''/console'' was not specified, what makes ''WinSCP.exe'' not show the console window, not to disturb you while you are using your workstation. \\ You can have WinSCP [[ui_generateurl\|generate the command-line template]] for you.
	* If your script uses local paths relative to the script path or WinSCP executable path, specify the respective path in //Start in// field.		* If your script uses local paths relative to the script path or WinSCP executable path, specify the respective path in //Start in// field.