Differences
This shows you the differences between the selected revisions of the page.
| 2015-01-27 | 2015-01-27 | ||
| start command not to block window (martin) | library_sessionoptions_parseurl + article (martin) | ||
| Line 18: | Line 18: | ||
| * 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 paths]]// 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 paths]]// 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]]). \\ In a script, you can make use of ''[[scripting#variables|%WINSCP_PATH%]]'' to refer to the WinSCP executable path. | + | * 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 ''[[scripting#variables|%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 windows is blocked, while the command is running. Should you want to avoid that, use ''start'' command: \\ <code batch> | * If the custom command refers to files (i.e. uses [[custom_command#patterns|patterns]] like ''!'', ''!&'', ''!^!''), WinSCP windows is blocked, while the command is running. Should you want to avoid that, use ''start'' 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 | ||
| Line 54: | Line 54: | ||
| ==== Passing Session Settings ==== | ==== Passing Session Settings ==== | ||
| - | As mentioned above use custom command pattern ''!S'' to pass the current session settings to the script. In the script, use ''SessionOption.ParseUrl'' to parse the URL. | + | As mentioned above use a custom command pattern ''!S'' to pass the current session settings to the script. In the script, use ''[[library_sessionoptions_parseurl|SessionOption.ParseUrl]]'' to parse the URL. |
| <code powershell> | <code powershell> | ||