Re: Clear command window?

I thought you said you get 8-10 job offers a week. So how is
that a destroyed career?

Robin S.
--------------------------------------------------
<aaron.kempf@xxxxxxxxx> wrote in message
news:1166390165.022522.288700@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
it's the single feature I wish that VB6 had.

I'll use my dirty mouth where I want.

MS Killed the world's popular language; they personally destroyed my
programming career.

I could give a ***.
I'll still use VB until the make VB10 and it will be 100% backwards
comptabile with VB.com

-Aaron



The Grim Reaper wrote:
Troll. Troll. Troll. TROLL.

Get a life, you sad POS.

<aaron.kempf@xxxxxxxxx> wrote in message
news:1166226435.165919.173320@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
yeah this is probably the ONE FEATURE THAT WAS MISSING IN VB6; AND
THEY
COULDN'T AFFORD TO FIX IT IN THREE NEW VERSIONS OF VISUAL STUDIO?

eat a ***, microsoft

-Aaron




Tim Zych wrote:
Wow. That looks very promising.

I assigned a shortcut key to it, but when I tried it during
runtime, it
didn't execute.

It seems to work only during design time.

Thanks. That's good stuff to know.


"Mythran" <kip_potter@xxxxxxxxxxx> wrote in message
news:egMcgjIIHHA.4216@xxxxxxxxxxxxxxxxxxxxxxx


"Tim Zych" <tzych@nononononEarth__LinkDotNet> wrote in message
news:emK1j57HHHA.4056@xxxxxxxxxxxxxxxxxxxxxxx
Is there keystroke combination that will clear the command
window in
Visual
Studio.Net?

Or, is there a way for me to clear it in vb.net code, prior to
my
code
running?

Thanks.






Edit.ClearAll is the command to use. You can bind this
command to a
keyboard shortcut by going to
Tools->Options->Environment->Keyboard
and
type in the 'Show commands containing:' textbox:
'Edit.ClearAll' w/o
the
quotes. Select the command and in the 'Press shortcut
key(s):' box,
press
the keyboard shortcut you wish to associate with clearing the
window...click Ok, and try it out :)

Please note, this command is available in .Net 2003, and I don't
have
2005
installed to test. The instructions above are also for 2003
:( Even
though
this is for 2003, it *should* still be available in .Net
2005...g'luck!

HTH,
Mythran






.