Hi Martin, thank you for the reply, i did have a play with it, at first I wasn't sure how to reference the .exe but did then realise as long as it's in the same directory as the .dll it gets picked up.

Yes, you just need to extract the "Automation" package anywhere you like:
https://winscp.net/eng/docs/library_powershell#install

And indeed, you can load the assembly from any directory you like:
https://winscp.net/eng/docs/library_powershell#loading
The assembly will look for the .exe in the same folder.

I have realised that putting WinSCP.exe and WinSCPnet.dll in the same location as the script works ok, is this the most efficient way to do it?

Rather than having many copies of those 2 files with different scripts, can I change the location the script looks at for them so I only need 1 copy of them in a central location which all scripts could reference?

Sorry if I have missed this in the docs.

Hi,

I'm looking to create a PowerShell form that will be given to people within the business to be able add files to an SFTP site.

What is the best way to manage this with WinSCP from a deployment point of view?
Ideally, I don't want to install WinSCP across different computers.

Can I put an .exe or .dll in a central location for all machines to use?

Cheers,
Jamie