Console crashes when started from .Net
I'm trying to use WinSCP, runtime, from a program I'm working on. I've already got PLink up and running and I'm going to use that for issuing commands. I'd like to use the WinSCP sychronize function for file transfer though :)
I was able to redirect the WinSCP output stream (.Net), but the WinSCP3.com crashes when I start the process (even if I don't redirect the stream). If I just remove the .exe, I get the output stream nice and tidy as it complains it can't find the file.
I looked up the error code, and it complained about some memory conflict (I think).
I also looked at a working .com file (started fom cmd) and compared it to a crashed one (started as a process in .Net), but the only difference seemed to be that the envornment keys (not values) in the latter one were all lowercase. The .com file also crashes After it has started the WinSCP.exe process (Problem communicating with WinSCP.exe?), which seems to be working fine... It lives on as a seperate process after the WinSCP.com is terminated.
Got a clue about this? :)
Arne
I was able to redirect the WinSCP output stream (.Net), but the WinSCP3.com crashes when I start the process (even if I don't redirect the stream). If I just remove the .exe, I get the output stream nice and tidy as it complains it can't find the file.
I looked up the error code, and it complained about some memory conflict (I think).
I also looked at a working .com file (started fom cmd) and compared it to a crashed one (started as a process in .Net), but the only difference seemed to be that the envornment keys (not values) in the latter one were all lowercase. The .com file also crashes After it has started the WinSCP.exe process (Problem communicating with WinSCP.exe?), which seems to be working fine... It lives on as a seperate process after the WinSCP.com is terminated.
Got a clue about this? :)
Arne