Differences
This shows you the differences between the selected revisions of the page.
| 2017-03-05 | 2017-03-07 | ||
| new package name format (martin) | breakup by ide/language (martin) | ||
| Line 9: | Line 9: | ||
| The binaries interact with each other and must be kept in the same folder for the assembly to work. In rare situations this is not possible (e.g. when [[#gac|installing the assembly to GAC]]), make use of the ''[[library_session#executablepath|Session.ExecutablePath]]'' property to force the assembly to look for the ''winscp.exe'' in a different location. | The binaries interact with each other and must be kept in the same folder for the assembly to work. In rare situations this is not possible (e.g. when [[#gac|installing the assembly to GAC]]), make use of the ''[[library_session#executablepath|Session.ExecutablePath]]'' property to force the assembly to look for the ''winscp.exe'' in a different location. | ||
| + | |||
| + | Further steps depend on a development environment/programming languages, that you will use with the assembly: | ||
| + | |||
| + | * PowerShell: No additional installations steps are needed. Read about [[library_powershell|using WinSCP .NET assembly from PowerShell]]. | ||
| + | * Visual Studio (C#, VB.NET): For development, you better use the [[#nuget|NugGet package]], instead of installing the assembly manually. The NuGet package will even care for configuring your project to deploy the assembly. | ||
| + | * [[library_vb|VBA]], [[library_com_wsh|VBScript, JScript]], [[library_perl|Perl]]: You need to [[#registering|register the assembly for COM]]. | ||
| ==== [[vs]] Using from Visual Studio or other Development or Runtime Environment ==== | ==== [[vs]] Using from Visual Studio or other Development or Runtime Environment ==== | ||