How to Show a Console Output/Window in a Forms Application

How do I show a console output/window in a forms application?

this one should work.

using System.Runtime.InteropServices;private void Form1_Load(object sender, EventArgs e){    AllocConsole();}[DllImport("kernel32.dll", SetLastError = true)][return: MarshalAs(UnmanagedType.Bool)]static extern bool AllocConsole();

How to use Console.WriteLine() in windows Forms Application

Console.WriteLine command is working only in console application type. so using windows app doesn't display required output,seems your application is windows form application.

if you want show output on Console window using Console.WriteLine withing the windows form application need to add this property and call it from the main form constructor.then it will open with console as well.

     public InsertNames()     {       AllocConsole();       InitializeComponent();     }      [System.Runtime.InteropServices.DllImport("kernel32.dll")]      private static extern bool AllocConsole();

OR

In project settings you can set application type as Console. Then you will get console and form as well.

Console output in WindowsForms application

Each process can have only at most one console associated with it. There are several paths you can take: either you hide the console window immediately on startup and show it later (via ShowWindow), or you leave the project as a window application, and create the console manually using AllocConsole later.

In the case you wanted multiple consoles, you can e.g. create a dummy process (cmd) and attach your process to its console, using AttachConsole. The managed way would be to use remoting or other techniques to communicate with the dummy process (with your own implementation), and print texts through that.

Show Console in Windows Application?

What you want to do is not possible in a sane way. There was a similar question so look at the answers.

Then there's also an insane approach (site down - backup available here.) written by Jeffrey Knight:

Question: How do I create an application that can run in either GUI
(windows) mode or command line / console mode?

On the surface of it, this would seem easy: you create a Console
application, add a windows form to it, and you're off and running.
However, there's a problem:

Problem: If you run in GUI mode, you end up with both a window and a
pesky console lurking in the background, and you don't have any way to
hide it.

What people seem to want is a true amphibian application that can run
smoothly in either mode.

If you break it down, there are actually four use cases here:

User starts application from existing cmd window, and runs in GUI modeUser double clicks to start application, and runs in GUI modeUser starts application from existing cmd window, and runs in command modeUser double clicks to start application, and runs in command mode.

I'm posting the code to do this, but with a caveat.

I actually think this sort of approach will run you into a lot more
trouble down the road than it's worth. For example, you'll have to
have two different UIs' -- one for the GUI and one for the command /
shell. You're going to have to build some strange central logic
engine that abstracts from GUI vs. command line, and it's just going
to get weird. If it were me, I'd step back and think about how this
will be used in practice, and whether this sort of mode-switching is
worth the work. Thus, unless some special case called for it, I
wouldn't use this code myself, because as soon as I run into
situations where I need API calls to get something done, I tend to
stop and ask myself "am I overcomplicating things?".

Output type=Windows Application

using System;using System.Collections.Generic;using System.Windows.Forms;using System.Runtime.InteropServices;using System.Diagnostics;using Microsoft.Win32;namespace WindowsApplication{    static class Program    {        /*    DEMO CODE ONLY: In general, this approach calls for re-thinking     your architecture!    There are 4 possible ways this can run:    1) User starts application from existing cmd window, and runs in GUI mode    2) User double clicks to start application, and runs in GUI mode    3) User starts applicaiton from existing cmd window, and runs in command mode    4) User double clicks to start application, and runs in command mode.    To run in console mode, start a cmd shell and enter:        c:\path\to\Debug\dir\WindowsApplication.exe console        To run in gui mode,  EITHER just double click the exe, OR start it from the cmd prompt with:        c:\path\to\Debug\dir\WindowsApplication.exe (or pass the "gui" argument).        To start in command mode from a double click, change the default below to "console".    In practice, I'm not even sure how the console vs gui mode distinction would be made from a    double click...        string mode = args.Length > 0 ? args[0] : "console"; //default to console    */        [DllImport("kernel32.dll", SetLastError = true)]        static extern bool AllocConsole();        [DllImport("kernel32.dll", SetLastError = true)]        static extern bool FreeConsole();        [DllImport("kernel32", SetLastError = true)]        static extern bool AttachConsole(int dwProcessId);        [DllImport("user32.dll")]        static extern IntPtr GetForegroundWindow();        [DllImport("user32.dll", SetLastError = true)]        static extern uint GetWindowThreadProcessId(IntPtr hWnd, out int lpdwProcessId);        [STAThread]        static void Main(string[] args)        {            //TODO: better handling of command args, (handle help (--help /?) etc.)            string mode = args.Length > 0 ? args[0] : "gui"; //default to gui            if (mode == "gui")            {                MessageBox.Show("Welcome to GUI mode");                Application.EnableVisualStyles();                Application.SetCompatibleTextRenderingDefault(false);                Application.Run(new Form1());            }            else if (mode == "console")            {                //Get a pointer to the forground window.  The idea here is that                //IF the user is starting our application from an existing console                //shell, that shell will be the uppermost window.  We'll get it                //and attach to it                IntPtr ptr = GetForegroundWindow();                int  u;                GetWindowThreadProcessId(ptr, out u);                Process process = Process.GetProcessById(u);                if (process.ProcessName == "cmd" )    //Is the uppermost window a cmd process?                {                    AttachConsole(process.Id);                    //we have a console to attach to ..                    Console.WriteLine("hello. It looks like you started me from an existing console.");                }                else                {                    //no console AND we're in console mode ... create a new console.                    AllocConsole();                    Console.WriteLine(@"hello. It looks like you double clicked me to start                   AND you want console mode.  Here's a new console.");                    Console.WriteLine("press any key to continue ...");                    Console.ReadLine();                       }                FreeConsole();            }        }    }}

windows form .. console.writeline() where is console?

In project settings set application type as Console. Then you will get console window and Windows form.

How do I show a console output/window in a forms application?

this one should work.

using System.Runtime.InteropServices;private void Form1_Load(object sender, EventArgs e){    AllocConsole();}[DllImport("kernel32.dll", SetLastError = true)][return: MarshalAs(UnmanagedType.Bool)]static extern bool AllocConsole();