I think the forcibly stopped comes from the reader application reading one line and exiting.
Can you put the read into a loop of some form?
If you're going to write to the stream more than once, you should probably read more than once.
You'll probably want to add detection for the stream closing to the reader after you start the loop.
And the read loop should block somewhere, either for the stream to be ready or for a time period. You don't want it running in a tight loop burning cpu cycles without a purpose.
Murtan
Practically a Master Poster
671 posts since May 2008
Reputation Points: 344
Solved Threads: 116
I think Murtan is right. Why don't you take a look in to "remoting" in C#. It basically allows you to call methods running on another computer. IE you have a 'server' application running on a remote machine and you can call methods and pass values. In this case you could make a serialized process list and transmit that across the pipe which would abstract away having to deal with sockets.
If you want to do sockets then please upload a sample project so we can take a look at what is causing the error.
sknake
Industrious Poster
4,954 posts since Feb 2009
Reputation Points: 1,764
Solved Threads: 735
This sounds like a browser error to me. Maybe you closed your browser before the submit? I don't know.
If a moderator deletes your post you will receive a private message in the forum stating that it has been deleted. Check your message box.
sknake
Industrious Poster
4,954 posts since Feb 2009
Reputation Points: 1,764
Solved Threads: 735