Allow native DLL to output stdout / stderr in c# console application
Posted
by xaw
on Stack Overflow
See other posts from Stack Overflow
or by xaw
Published on 2010-04-03T02:02:34Z
Indexed on
2010/04/03
2:03 UTC
Read the original article
Hit count: 333
I have a native DLL which outputs via stdout / stderr.
I have a C# console application which calls this DLL and outputs binary data to a parent C# application which started the C# console exe, processing stdout / stderr.
Currently when I call the C# exe it works just fine (the DLL hooks up to the stdout of my console application and puts its data in just fine).
Is this by design (and shouldn't be broken in future .NET framework versions)?
Are there limitations on my managed code's deployment with this strategy (full-trust, permission requirements, GAC issues, etc)?
I can't seem to find any documentation about stdout with a managed exe and an unmanaged dll both putting data in that standard output on MSDN.
Thanks,
© Stack Overflow or respective owner