Re: Redirecting sdtin, stdout, stderr from an already running process
- From: Jeroen Mostert <jmostert@xxxxxxxxx>
- Date: Mon, 03 Mar 2008 18:31:01 +0100
ghandi wrote:
On Mar 2, 5:59 am, Jeroen Mostert <jmost...@xxxxxxxxx> wrote:> Thanks again for your time. I'll try a few more things and then tryJeroen Mostert wrote:
<snip>> A much simpler approach is to use impersonation, then use Process tostart the process regularly:<snip>This, finally, works on my system. Is it of use to you too?Never mind, of course this doesn't work, and I'm a very sloppy tester.
Really, by this point, I can really only advise two courses of action:
- Give up and accept that there will be a window.
- After the process has started, use ugly code to find the window and hide
it manually.
Doing it "properly" is way, way more trouble than its worth.
one of the things you mentioned (probably give up and accept that
there will be a window). I was also looking at the new namespace
System.IO.Pipes. It has an AnonymousPipeServerStream that might be
useful.
If you don't mind the dependency on .NET 3.5 (since that's when they were introduced) then using the native pipe classes is definitely preferable to rolling your own. (I only recently discovered them myself, otherwise I would have recommended them.)
--
J.
.
- References:
- Re: Redirecting sdtin, stdout, stderr from an already running process
- From: Jeroen Mostert
- Re: Redirecting sdtin, stdout, stderr from an already running process
- From: Jeroen Mostert
- Re: Redirecting sdtin, stdout, stderr from an already running process
- From: ghandi
- Re: Redirecting sdtin, stdout, stderr from an already running process
- Prev by Date: Marshaler bug with VBScript arrays
- Next by Date: Add-in and field value in table
- Previous by thread: Re: Redirecting sdtin, stdout, stderr from an already running process
- Next by thread: Re: Marshal::StringToHGlobalAnsi and System.AccessViolationException
- Index(es):
Relevant Pages
|