How can you get rid of that console window (the place where the printf's and scanf's go) when you're creating an exclusive GUI app that doesn't need one ?

Use WinMain instead of main.
WinMain has a different prototype:

int WINAPI WinMain (
    HINSTANCE hInstance, // handle to current instance
    HINSTANCE hPrevInstance, // handle to previous instance
    LPSTR lpCmdLine, // pointer to command line
    int nCmdShow  // show state of window
   );



Use a .DEF file when you link with at least:

EXETYPE NT
SUBSYSTEM WINDOWS



pramod wrote:

> How can you get rid of that console window (the place where the printf's and scanf's go) when you're creating an exclusive GUI app that doesn't need one ?

Jan Knepper wrote:

> Use WinMain instead of main.
> WinMain has a different prototype:
>
> int WINAPI WinMain (
>     HINSTANCE hInstance, // handle to current instance
>     HINSTANCE hPrevInstance, // handle to previous instance
>     LPSTR lpCmdLine, // pointer to command line
>     int nCmdShow  // show state of window
>    );
>
> Use a .DEF file when you link with at least:
>
> EXETYPE NT
> SUBSYSTEM WINDOWS

Actually...
You might want to use a .DIF file as:

NAME "Name"
DESCRIPTION 'Description'
EXETYPE    NT
SUBSYSTEM    WINDOW,4.0
STUB    'WINSTUB.EXE'
CODE    EXECUTE READ
DATA    READ WRITE

The "SUBSYSTEM WINDOW,4.0" allows you to use the latest (Windows 95) controls.


> pramod wrote:
>
> > How can you get rid of that console window (the place where the printf's and scanf's go) when you're creating an exclusive GUI app that doesn't need one ?

Try the following compiler switch: -L/exet:nt/su:windows
This works fine for me.
Good Luck!

>
>How can you get rid of that console window (the place where the printf's and scanf's go) when you're creating an exclusive GUI app that doesn't need one ?
>
>