Differences

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

2016-10-10 2016-11-10
the details matter, as people keep asking for them + usage of the executable via its public scripting interface is actually important in the respect to the GPL license (martin) intended anchor (martin)
Line 4: Line 4:
The assembly is also exposed to COM, and as such it can be used from variety of other programming languages and development environments--e.g., [[library_com_wsh|WSH-hosted active scripting languages]] like JScript and VBScript, [[library_vb|Visual Basic for Applications (VBA)]], [[library_perl|Perl]], and Python. The assembly is also exposed to COM, and as such it can be used from variety of other programming languages and development environments--e.g., [[library_com_wsh|WSH-hosted active scripting languages]] like JScript and VBScript, [[library_vb|Visual Basic for Applications (VBA)]], [[library_perl|Perl]], and Python.
-The library is primarily intended for advanced automation tasks that require conditional processing, loops or other control structures for which the basic [[scripting|scripting interface]] is too limited. The library is not a general purpose file transfer library. It particularly lacks support for interactive processing and as such it is not well suited for use in GUI applications.+The library is primarily ==intended== for advanced automation tasks that require conditional processing, loops or other control structures for which the basic [[scripting|scripting interface]] is too limited. The library is not a general purpose file transfer library. It particularly lacks support for interactive processing and as such it is not well suited for use in GUI applications.
You can write a script using the assembly that [[guide_custom_commands_automation|extends functionality of WinSCP GUI]]. You can write a script using the assembly that [[guide_custom_commands_automation|extends functionality of WinSCP GUI]].

Last modified: by martin