Re: Clear command window?

yeah.. I do do plenty of VB6 still.

i just don't see long term growth for that; because Microsoft has
killed off the language.

I think that you are confusing me with MP.. but yeah of course I write
VB6 every day.
it's called 'Access Data Project' no DLL hell, nothing difficult to
deal with.

just simple data entry and reporting.. and a couple of intranet sites
here and there.

-Aaron



RobinS wrote:
I thought you said you have plenty of VB6.0 work, and that's why
you've not been around as much, it's because you've been so busy
doing your VB6.0 work that's just overflowing your inbox. So which
is it? You can't have it both ways. You can't say they killed your
programming career in one thread while saying you have more work
than you can do in VB6 someplace else. Or am I confusing you with
MP? If I am, maybe he could throw some work your way.

Robin S.
------------------------------------
<aaron.kempf@xxxxxxxxx> wrote in message
news:1166561577.733135.166250@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
notice the differentiation between 'programming' and 'database'

they killed my programming career-- it was the worlds' most popular
programming language.. and now it's just GONE.

and I for one; have the BALLS to stand up for the users of the worlds'
most popular programming language.

If they're going to change VB every other year for the next 10 years;
I
just dont know if I see the point.

They already changed it fom VB6 to VB.net 2002 to VB.net 2003 to VB
2005.

they change the programming name THREE TIMES IN FIVE YEARS?
someone somewhere needs to stop coming up with corny cheesy monikers;
stop RENAMING NEWSGROUPS EVERY RELEASE -- I AM IN A NEWSGROUP NAMED
DOTNET TALKING ABOUT A LANGUAGE THAT ISNT CALLED DOTNET? WTF- LIKE
SERIOUSLY?

they screwed over the programmers of the world; I can literally coast
by on my database skills and never have to write another line of code
in my life

I've got bigger fish to fry-- like Olap for example. Screw
Programming.
I'll just use PHP against XMLA web services and everyone will be
happy.

-Aaron




RobinS wrote:
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






.