Why Does Console.WriteLine() Not Write to Command Window?

[joey.powell]

I have a windows form app in C# in VS2005. In the "program.cs" file, I
take some command line arguments and use "Console.WriteLine("fsdfsd")
to give feedback to users. When I step through the program, the code
block is executing, but no text is written to the command line.

What might be causing this?

[Marc Gravell]

Quite simply, windows apps don't connect to a console.

It can either be console or winform; Not both. This is part of the PE
header so is more Windows than .Net.

You could perhaps have 2 exes (one winform, one console).
Trace.WriteLine can be useful, as this will appear in the debugger by
default, or can be redirected.

Marc

[=?iso-8859-1?q?Horacio_Nu=F1ez_Hern=E1ndez?=]

Is just a thought but. why you dont try:

console.WriteLine("...");
Application.Run(new Form1);
-------------
An additional way is change the propertys in,out of the
System.Console, they are streams so you could put text files on

cheers,

[Samuel R. Neff]

put a breakpoint on the first line of your app and inspect
System.Console.Out. You'll see that it's ultimately a wrapper around
System.IO.Stream.NullStream.

((System.IO.StreamWriter)(((System.IO.TextWriter.S yncTextWriter)(System.Console.Out))._out)).BaseStr eam

Use a logging framework instead of console.writeline (I'd suggest
log4net).

HTH,

Sam

------------------------------------------------------------
We're hiring! B-Line Medical is seeking .NET
Developers for exciting positions in medical product
development in MD/DC. Work with a variety of technologies
in a relaxed team environment. See ads on Dice.com.

On 3 May 2007 11:56:25 -0700, jo*********@topscene.com wrote:

>I have a windows form app in C# in VS2005. In the "program.cs" file, I
take some command line arguments and use "Console.WriteLine("fsdfsd")
to give feedback to users. When I step through the program, the code
block is executing, but no text is written to the command line.

What might be causing this?

[Michael A. Covington]

<jo*********@topscene.comwrote in message
news:11**********************@o5g2000hsb.googlegro ups.com...

>I have a windows form app in C# in VS2005. In the "program.cs" file, I
take some command line arguments and use "Console.WriteLine("fsdfsd")
to give feedback to users. When I step through the program, the code
block is executing, but no text is written to the command line.

What might be causing this?

You've told the compiler that you have a windowed application. If you will
tell the compiler to compile it as a console app (which is somewhere in
Project Properties), you'll get a console window, and the forms will all
still work. This is a handy secret.

Or use System.Diagnostics.Debug.WriteLine(...) to write in the debug window
in VS2005 while the program runs.

[Michael A. Covington]

"Marc Gravell" <ma**********@gmail.comwrote in message
news:11*********************@c35g2000hsg.googlegro ups.com...

Quite simply, windows apps don't connect to a console.

It can either be console or winform; Not both. This is part of the PE
header so is more Windows than .Net.

Little-known fact: Actually it *can* be both. Take a Windows Forms app and
compile it as a console app, and you'll have a console window.

You can also use Win32 calls to create a console and attach a stream to it.

[Chris Nahr]

On Fri, 4 May 2007 00:37:33 -0400, "Michael A. Covington"
<lo**@ai.uga.edu.for.addresswrote:

>Little-known fact: Actually it *can* be both. Take a Windows Forms app and
compile it as a console app, and you'll have a console window.

Not really, it's actually a console application that pops up a window.
The original console window stays visible all the time.
--
http://www.kynosarges.de