windows-shell

I have a commandline application coded in delphi that I need to call from a normal desktop application (also coded in delphi). In short, I want to call the commandline app and display the text it outputs "live" in a listbox. It's been ages since I have played around with the shell, but I distinctly remember that in order to grab the text from a commandline app - I have to use the pipe symbol ">". Like this: C:/mycmdapp.exe >c:/result.txt This will take any text printed to the shell (using writeLn) and dump it to a textfile called "result.txt". But.. (and here comes the pickle), I want a live

I'm looking for the .NET-preferred way of performing the same type of thing that ShellExecute does in Win32 (opening, printing, etc. for arbitrary file types). I've been programming Windows for over 20 years, but I'm a complete newbie at .NET, so maybe I'm just looking in the wrong places. I'm currently using .NET 2.0 (VS C# 2005), but could use VS 2008 if need be. If the only answer is to use P/Invoke, then I might be better just writing my small utility using Win32 anyway. Process.Start . Note that advanced uses (printing etc) require using a ProcessStartInfo and setting the Verb property.

I was wanting to write a simple windows shell extension to add to the context menu, and C# is the language I most use these days. Is it a decent choice for a shell extension? Are the interfaces easy to get to with it? Is there additional overhead that causes the menu to be slower to pop up? Any one have good pointers for getting started? GSerg A Raymond's post: Do not write in-process shell extensions in managed code . A recent follow-up: Now that version 4 of the .NET Framework supports in-process side-by-side runtimes, is it now okay to write shell extensions in managed code? The bottom line