Re: FTP DLL for commercial use
« Reply #3 on: Jun 23rd, 2016, 2:35pm »
Funny nobody pointed out my mistake. The old ftp4win32.dll is discontinued and has no license attached. I was looking at the wrong web page before. It has been replaced with a different program that looks GUI only for the client part:
At any rate winSCP has a .NET DLL with the Mozilla (more liberal than GPL?) license which can talk to the exe which should avoid having to write to disk if using a named pipe API fails. I know I've tried to use a named pipe with common windows commands and had them fail on me. If anybody knows why it could be educational. I did get it to work with a non-windows executable.