Downloading and Installing WinSCP .NET Assembly

WinSCP .NET assembly is available in a separate package named winscpXXXautomation.zip on WinSCP download page. Follow the .NET assembly/COM library link.

To use the assembly, you need to have WinSCP installed (or download the portable package). You have to use the same version of the assembly as your version of WinSCP.

WinSCP .NET assembly interacts with WinSCP executables (winscp.com and winscp.exe). By default it looks for the executables in the same folder, where the assembly is stored. For that reason, you should extract the package into the same folder, where you have WinSCP installed/extracted. You can also copy all binaries (winscp.com, winscp.exe and winscp.dll) into separate folder.

If you cannot store the assembly into the same folder, you can alternatively make use of Session.ExecutablePath property to force the assembly to look for the WinSCP executables in a different location.

Note that your runtime or development environment may copy the assembly into an another location. In that case you need to copy WinSCP executables into that location too. E.g. If you reference WinSCP assembly from your project in Microsoft Visual Studio, it copies the assembly during build into the project Output path (e.g. <your_project_path>/obj/Debug). Similar case is when you install the assembly into Global Assembly Cache (GAC), e.g. when registering the assembly for COM.

When deploying the assembly, make sure that WinSCP is installed along with the assembly on the target system and that WinSCP assembly can find the WinSCP executables.