
The NuGet package will even care for configuring your project to deploy the assembly. Visual Studio (C#, VB.NET): For development, you better use the NugGet package, instead of installing the assembly manually.PowerShell: No additional installations steps are needed.when installing the assembly to GAC), make use of the Session.ExecutablePath property to force the assembly to look for the winscp.exe in a different location.įurther steps depend on a development environment/programming languages, that you will use with the assembly: In rare situations this is not possible (e.g.

The binaries interact with each other and must be kept in the same folder for the assembly to work. The package includes the assembly itself ( winscpnet.dll) and a required dependency, WinSCP executable winscp.exe.
