C# adding a console window in a windows app

[NotSoSmartGuy]

Basically I have a windows app and would like to add a console window where I can output Console.WriteLine("SSSSSSSSSSSSSSSS");

[still1]

  On 26/05/2010 at 18:37, NotSoSmartGuy said:

Basically I have a windows app and would like to add a console window where I can output Console.WriteLine("SSSSSSSSSSSSSSSS");

embedding a console in windows app or opening a new console windows from windows app?

[NotSoSmartGuy]

opening a new console window, so I can check what I am doing

[hdood]

I don't think there is any .NET call for that, but the native function is AllocConsole and you could call that with interop:

[DllImport("kernel32")]
static extern int AllocConsole();

static void Main()
{
        AllocConsole();
}

If you call AllocConsole before calling any console functions, that should be all you need. Otherwise you need to also manually set up stdout and friends. FreeConsole is the opposite of AllocConsole, and is used to get rid of the console.

[still1]

using System.Runtime.InteropServices;

[DllImport("kernel32.dll", EntryPoint = "AllocConsole", SetLastError = true, CharSet = CharSet.Auto, CallingConvention = CallingConvention.StdCall)]

private static extern int AllocConsole();

AllocConsole();

Console.WriteLine("Hello World!"); // outputs to console window

[boogerjones]

Wouldn't it make more sense for a GUI app to have a dialog/form/whatever with a textbox that you write to instead? Is there something about the console that you specifically need? If you're just trying to "check what you're doing," I think allocating a console is inappropriate. Especially since the Windows console hasn't changed since Windows 98

It's usually better to tell us what goal you're trying to achieve. Lots of people use the wrong tool for the job.

[hdood]

The console is a quick and useful way of outputting debug messages.

[the_architect]

  On 26/05/2010 at 22:23, hdood said:

The console is a quick and useful way of outputting debug messages.

Check out the Debug.Writeline method if you are using Visual Studio, this is an easy way of outputting debug messages http://msdn.microsoft.com/en-us/library/system.diagnostics.debug.writeline.aspx

[hdood]

  On 26/05/2010 at 23:07, luke_smily_face said:

Check out the Debug.Writeline method if you are using Visual Studio, this is an easy way of outputting debug messages http://msdn.microsoft.com/en-us/library/system.diagnostics.debug.writeline.aspx

I do not write managed code, but presumably it is equivalent to the native debugging functions, which means you actually have to have a debugger attached in order to see the output. Sometimes you just want to display debug messages without the need for that.

[ReDwAvE]

Easy, Just go to the property of the project and make the Application Type : Console Application

and Writes Console.WriteLine() :)

[Rudy]

  On 27/05/2010 at 09:21, ReDwAvE said:

Easy, Just go to the property of the project and make the Application Type : Console Application

and Writes Console.WriteLine() :)

That's not what he wants. His application is NOT a console application but he still wants to send text to a console. A solution has already been posting anyway

[klay]

  On 27/05/2010 at 17:54, Rudy said:

That's not what he wants. His application is NOT a console application but he still wants to send text to a console. A solution has already been posting anyway

From the smiley face above you should have realized he was joking.

[Rudy]

  On 28/05/2010 at 03:17, klay said:

From the smiley face above you should have realized he was joking.

Even with the smiley face it doesn't seem like he's joking...

[Joddie]

  On 26/05/2010 at 23:07, luke_smily_face said:

Check out the Debug.Writeline method if you are using Visual Studio, this is an easy way of outputting debug messages http://msdn.microsoft.com/en-us/library/system.diagnostics.debug.writeline.aspx

Use this instead of console, visual studio will then output this for you internally instead of having one extra window spawning for your console, that also goes away if your program crashes.

If you need to read debug-output from deployed applications or similar have a look on Log4Net(http://logging.apache.org/log4net/index.html) that allows you to configure exactly how you want your debug lines to be output (console/debug, file, to server etc)

[Matthew S.]

Your not writing managed code but you are using C# :/

[Rudy]

  On 30/05/2010 at 10:16, FusionOpz said:

Your not writing managed code but you are using C# :/

He might not understand what "managed" code is

[hdood]

  On 30/05/2010 at 10:16, FusionOpz said:

Your not writing managed code but you are using C# :/

Are you talking to me? I do not write managed code in C# or any other language, but I can still guess the answer to simpler questions. I said this to make it clear that I had no expertise and was guessing that it was equivalent to certain native APIs. I was saying that a console can be useful because you sometimes want to output certain information to something other than a debugger. The two complement each other, it's not one or the other.

[Matthew S.]

  On 31/05/2010 at 05:46, hdood said:

Are you talking to me? I do not write managed code in C# or any other language, but I can still guess the answer to simpler questions. I said this to make it clear that I had no expertise and was guessing that it was equivalent to certain native APIs. I was saying that a console can be useful because you sometimes want to output certain information to something other than a debugger. The two complement each other, it's not one or the other.

Ah was somehow confusing you with the OP :p :whistle: *sneaks out the back door*