Differences
This shows you the differences between the selected revisions of the page.
| 2016-07-29 | 2016-07-29 | ||
| 5.9 installs the assembly (martin) | grammar (martin) | ||
| Line 16: | Line 16: | ||
| * Both PowerShell script and WinSCP script are to be executed locally using path to the remote files, so make sure you select //Local command// [[custom_command#types|type]] and //[[ui_customcommand|Use remote files]]// option. | * Both PowerShell script and WinSCP script are to be executed locally using path to the remote files, so make sure you select //Local command// [[custom_command#types|type]] and //[[ui_customcommand|Use remote files]]// option. | ||
| - | * The application run as a custom command (be it ''powershell.exe'' or WinSCP in a console mode) is executed in WinSCP startup directory, not in a WinSCP [[executable]] directory, nor directory shown in local panel (in [[ui_commander|Commander interface]]). \\ So generally, you should use a full path to a local files, both in the custom command itself (particularly for a path to WinSCP executable and path to the script) and the script (including a [[library_powershell#loading|path to WinSCP .NET assembly]]). \\ You can make use of ''[[local_path|%WINSCP_PATH%]]'' to refer to the WinSCP executable path. | + | * The application run as a custom command (be it the ''powershell.exe'' or WinSCP in a console mode) is executed in WinSCP startup directory, not in a WinSCP [[executable]] directory, nor directory shown in a local panel (in [[ui_commander|Commander interface]]). \\ So generally, you should use a full path to local files, both in the custom command itself (particularly for a path to WinSCP executable and path to the script) and the script (including a [[library_powershell#loading|path to WinSCP .NET assembly]]). \\ You can make use of ''[[local_path|%WINSCP_PATH%]]'' to refer to the WinSCP executable path. |
| * If the custom command refers to files (i.e. uses [[custom_command#patterns|patterns]] like ''!'', ''!&'', ''!^!''), WinSCP window is blocked, while the command is running. Should you want to avoid that, use the ''start'' command. Though note this prevents WinSCP from uploading files back to the server, if they were modified by the command. \\ <code batch> | * If the custom command refers to files (i.e. uses [[custom_command#patterns|patterns]] like ''!'', ''!&'', ''!^!''), WinSCP window is blocked, while the command is running. Should you want to avoid that, use the ''start'' command. Though note this prevents WinSCP from uploading files back to the server, if they were modified by the command. \\ <code batch> | ||
| cmd.exe /c start powershell.exe -File c:\example\example.ps1 | cmd.exe /c start powershell.exe -File c:\example\example.ps1 | ||