I need to use the WinSCPNet application in SmartConnect 21 instead of the built-in FTP connector that is available.
I was following the blog article, Using WinSCP and a task to upload or download files from an SFTP site, and in the Script Namespace section, it says that I need to add the WinSCPNet assembly to the Script Namespace window. However, when I do this, I get an error in SmartConnect and this fails with the error:
Could not load assembly ‘WinSCPNet’
Why isn’t this working, and how do I add the namespace properly?
The problem is that SmartConnect/.NET cannot find the WinSCPnet.dll where .NET is probing for the file.
If you’d like to watch a video explaining this, see below or click here.
Out of the box, an application that tries to load an assembly looks only in either the GAC – where we set the destination location- or else the Root application folder.
The WinSCP application installer did not install it to the GAC – and while it could do this, the easiest solution is to just copy the WinSCPnet.dll from the installation folderto the “Root” SmartConnect application folder per the referenced KB.
On SmartConnect 21, the default SmartConnect path is:
C:\Program Files\eOne Solutions\SmartConnect
On SmartConnect 2018, the default SmartConnect path is:
C:\Program Files (x86)\eOne Solutions\SmartConnect
Once the WinSCPnet.dll is copied into the SmartConnect folder, try to re-add the WinSCPnet namespace again, and it should be found and added properly without error.
