Latest winscp.dll file

Hi all;

So first I'll preface this with be gentle with me I'm new at this type of thing. :D
I'm troubleshooting a previously working environment that was transferred to a new environment due to an upgrade. I have a batch file that runs a PowerShell script that will run fine manually but not when it is scheduled as a windows task or as a Scribe preprocess job. So I've come to this site to try to learn about WinSCP and figure out why its not working now. I downloaded and installed the latest WinSCP application and overwrote the older WinSCP files only to discover that the winscp.dll file is not of the same version of the application. To start off, my first question is if I want to completely upgrade to the latest WinSCP, where do I get the latest winscp.dll file? Am I missing a critical step?

Note: when trying to run my scripts from the windows task schedule or Scribe, I get the message "Could not load file or assembly 'file:///C:\Windows\system32\WinSCP.dll' or one of its dependencies. The system cannot find the file specified.". So I know something is amok although I'm using a fully admin account.

Honestly I've read a lot on this site but my head is spinning; what I really need is some direction. If the WinSCP.dll, WinSCP.exe, Winscp.com, WinSCP.ini is all in the same directory as my bat file AND my powershell script (which references the dll in same directory), do I need to register anything? Do I need this winscpnet.dll as well? I don't have it in the old environment so I've been ignoring that.

Thanks for reading!

The .NET assembly binary is named WinSCPnet.dll is the latest release. It was renamed while back (originally it was winscp.dll).

So if you are upgrading, make sure you remove the winscp.dll and update the the DLL name everywhere you reference it (like in the PowerShell script).

martin wrote:

The .NET assembly binary is named WinSCPnet.dll is the latest release. It was renamed while back (originally it was winscp.dll).

So if you are upgrading, make sure you remove the winscp.dll and update the the DLL name everywhere you reference it (like in the PowerShell script).

Thank you. I was able to register everything successfully. I've also changed my reference to winscp.dll in the code to WinSCPnet.dll. I had to also change my connection code but everything works perfectly now and runs inside a scheduled scribe job. I'm a happy lady.

Thanks for the help!