Re: How to make the "Output" window show while running a program from

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



hi Feng


press Ctrl + Alt + o

and there it is

Michel Posseth [MCP]







"Feng" <Feng@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C0B82F6E-4577-41A2-85CB-B0BD8902D85F@xxxxxxxxxxxxxxxx
>I am debugging my code from VS.Net and need to watch my console.wirteline
> messages as I run the code. The problem is, as soon as my code starts
> running
> in debugging mode, the console window ("Output" window) will disappear and
> it
> only comes back when the program ends. How do I keep that window up so I
> can
> watch the message come out as the program runs?
>
> Thanks
>
> Feng


.



Relevant Pages

  • RE: VS.NET 2003 Debugger hangs.
    ... object properties in the watch window, ... > do with this problem because when debugging the client only the issue never ... > hangs and is irrespective of how I step through the code. ...
    (microsoft.public.vsnet.debugging)
  • Re: How to make the "Output" window show while running a program from
    ... > as my code starts running in debugging mode, ... > ("Output" window) will disappear and it only comes back when the ... How do I keep that window up so I can watch the message ... display and even record this output window. ...
    (microsoft.public.dotnet.languages.vb)
  • How to make the "Output" window show while running a program from
    ... I am debugging my code from VS.Net and need to watch my console.wirteline ... the console window will disappear and it ... Prev by Date: ...
    (microsoft.public.dotnet.languages.vb)
  • Re: How to make the "Output" window show while running a program from
    ... >I am debugging my code from VS.Net and need to watch my console.wirteline ... the console window will disappear and ... Prev by Date: ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Application.screenupdating always True?
    ... Application.Screenupdating can have no effect while single stepping - each step releases control to the OS, which will refresh every application window - and it is, in effect, True at every breakpoint. ... It seems possible that the Watch Window might be reflecting this - if you set a break on change it does break, and then breaks again after the next statement so it seems as though it might be getting a little confused. ... I wrote a test routine that set Screenupdating to false and then retested it then back to true 100 times - no break occurred; the question is essentially: if someone else has code that sets screenupdating to false and looks at the value in the watch pane while single stepping, do they see the value become false? ... Instead I try to use the Range object ...
    (microsoft.public.word.vba.general)