I am really out of my depth here. I will come back to this when I have a bit more breathing room. It is unfortunate that National Instruments is slow to upgrade the dot-net framework used with their projects, I can fully understand any reluctance to help with down-grading working code.

private void queueUserWorker() { }

ThreadPoolHelper.QueueUserWorkItem(queueUserWorker);

correct?

You can probably get rid of the System.Linq using statement since that is part of .NET 3.0. I don’t think I’m using any Linq in that project. ThreadingUtilities is the other DLL project in the download that provides the typesafe wrappers to ThreadPool.QueueUserWorkItem (as ThreadPoolHelper.QueueUserWorkItem). I have a couple posts around here on the blog explaining how that works.

Good luck!

I have started a project and got stuck on some dot-net framework things, as well as a dependency.

I can’t find System.Linq, I think this is a > 2.0 thing.
What is this:
using ThreadingUtilities;

Many thanks for the help!

Glad you like it

That block of code is using a lot of the syntactic sugar that C# 3.0 lets you do. Anything of the form (parm1,parm2…) => {…; return ___;} is an anonymous method. It’s just a method that takes two parameters and returns something (or not). The compiler can infer the type of the arguments and the return value.

In that example, I could have defined a method “private void OnOutputDataReceived(object sender, EventArgs args)” and then done “p.OutputDataReceived += OnOutputDataReceived;”. This is still shorthand — the verbose way of saying this is to do “p.OutputDataReceived += new OutputDataReceivedEventHandler(OnOutputDataReceived);”

They’re all equivalent in terms of the compiled code, but hooking up anonymous methods directly to the events can come in handy.

You’ll probably need the ErrorDataReceived event: http://msdn.microsoft.com/en-us/library/system.diagnostics.process.errordatareceived.aspx
You could also just hook into this event and add the text to the same text box if you wanted. (i.e. put but stderr and stdout into the same box).

As for piping text into the input stream, I think you can hook up a StreamWriter to the StandardInput stream: http://msdn.microsoft.com/en-us/library/system.diagnostics.process.standardinput.aspx

Hope that helps! I’d be really interested in seeing your final demo showing how to read/write to all 3 streams

I want to add a much smaller (3-line high) stderr window, and a single line with a Send button so someone can send text to stdin. I would simply deactivate the run button and input command line.

However, I do not understand this construct:

p.OutputDataReceived += (o, args) =>

{

string text = args.Data + Environment.NewLine;

uiThread.Invoke(() =>

{

txtOutput.AppendText(text);

});

};

What does this (o,args) => { block } syntax mean?

I’ll submit my code if I can get it to work.