If you wish to access standard input and output in your WPF app, you will have to compile it as a Console app and fire up the WPF application object manually.<\/p>\n
Sample application: https:\/\/github.com\/ikriv\/WpfStdOut<\/a>.<\/p>\n Attaching to the parent process console, as proposed by this CSharp411 article<\/a> (thanks to Roel van Lisdonk<\/a> for the pointer) insists on writing to the actual console and does not work well with redirected output.<\/p>\n Steps to apply to your application:<\/p>\n The downside is that when you run the WPF app from a shortcut, it will show a black console window in the background. This window can be hidden as described in this StackOverflow article<\/a>.<\/p>\n This is not a major problem though, since the purpose of the console output is to either show it in the command line window, or to redirect it to a file or some stream. Push come to shove, one can create a start that launches the “console” application with a detached console (ProcessStartInfo.CreateNoWindow<\/a>).<\/p>\n","protected":false},"excerpt":{"rendered":"\n
Console.Out.WriteLine()<\/code>, but it would not go anywhere.<\/li>\nProgram.cs<\/code> file with the following boilerplate code:\n[STAThread]\r\npublic<\/span>\u00a0static<\/span>\u00a0void<\/span>\u00a0Main(string<\/span>[]\u00a0args)\r\n{\r\n\u00a0\u00a0\u00a0\u00a0var<\/span>\u00a0app\u00a0=\u00a0new<\/span>\u00a0App<\/span>();\r\n\u00a0\u00a0\u00a0\u00a0app.InitializeComponent();\r\n\u00a0\u00a0\u00a0\u00a0app.Run();\r\n}<\/pre>\n<\/li>\nYourNamespace<\/i>.Program<\/code>.<\/li>\n