> "Frank Rizzo" <n***@none.com> wrote in message
> news:uQyZqVcJGHA.312@TK2MSFTNGP09.phx.gbl...
>> Ken Halter wrote:
>>> "Frank Rizzo" <nospam@nospam.com> wrote in message
>>> news:OOT3WFXJGHA.3732@TK2MSFTNGP10.phx.gbl...
>>>> a command window that works more or less like in VB6.
>>> Your "more or less like" needs to change to "nothing like" imo.
>> What do you mean "nothing like"?  You type in a command and it executes
>> just like in vb6.  What are you referring to?
>
> Well... in the VB6 IDE I have right in front of me, there's no window called
> "Command" for one thing. For another, try pasting a block of text into *any*
> window (except a code window) that .Net provides. If you manage to find one
> that even accepts a block of text, try changing any part of that text,
> select the block again and try to paste it into a code window.

"Frank Rizzo" <n***@none.com> wrote in message
news:OgtQGWdJGHA.1028@TK2MSFTNGP11.phx.gbl...
>>
>> Well... in the VB6 IDE I have right in front of me, there's no window
>> called "Command" for one thing. For another, try pasting a block of text
>> into *any* window (except a code window) that .Net provides. If you
>> manage to find one that even accepts a block of text, try changing any
>> part of that text, select the block again and try to paste it into a code
>> window.
>
> I meant the Immediate window, I think you know this.  In VS.NET 2003 it is
> called Command Window - Immediate.  In vs 2005, it is simply called
> Command Window.  I agree that it doesn't work exactly as VB (more like Dos
> window), functionally the result is the same.
>
>> There's a hellofalot more to VBs immediate window that simply being able
>> to "run A command". I can "run A command" using a DOS window too. That
>> doesn't make it anywhere close to VBs immediate window.
>
> Specifically and functionally, what can't you do in vs 2005 command
> window?

> "Frank Rizzo" <n***@none.com> wrote in message
> news:OgtQGWdJGHA.1028@TK2MSFTNGP11.phx.gbl...
>>> Well... in the VB6 IDE I have right in front of me, there's no window
>>> called "Command" for one thing. For another, try pasting a block of text
>>> into *any* window (except a code window) that .Net provides. If you
>>> manage to find one that even accepts a block of text, try changing any
>>> part of that text, select the block again and try to paste it into a code
>>> window.
>> I meant the Immediate window, I think you know this.  In VS.NET 2003 it is
>> called Command Window - Immediate.  In vs 2005, it is simply called
>> Command Window.  I agree that it doesn't work exactly as VB (more like Dos
>> window), functionally the result is the same.
>>
>>> There's a hellofalot more to VBs immediate window that simply being able
>>> to "run A command". I can "run A command" using a DOS window too. That
>>> doesn't make it anywhere close to VBs immediate window.
>> Specifically and functionally, what can't you do in vs 2005 command
>> window?
>
> Paste a block of text. Modify a block of text. Copy a block of text (see the
> pattern here? <g>)
>
> VB6's immediate window = Notepad on steroids. There's nothing like that in
> .Net, period. If I want to modify a block of text, the only option is to
> place that block in the code window or a separate text editor. Neither of
> which I have interest in doing on a regular basis.

>

"Frank Rizzo" <nospam@nospam.com> wrote in message
news:OOT3WFXJGHA.3732@TK2MSFTNGP10.phx.gbl...
> Lenny Abbey wrote:
> > Is VB2005 a new version in the .NET series? Or does it reintroduce
elements
> > from VB6?
> >
> > Which family tree does it reside in?
>
> It is firmly rooted in the .NET world.  However, it has re-introduced
> things like Edit & Continue, better intellisense and a command window
> that works more or less like in VB6.  But all of these technologies are
> now underpinned by .NET
>
> > I am beginning to have some customer resistance because the VB6
installer is
> > so out of sync with current file versions. My users balk at having to
read
> > the clumsy warning box about files being newer or older. So I have some
> > incentive to move on. But I hate to abandon 20 years of experience with
> > BASIC.
>
> That has nothing to do with VB, I have never used that installer that
> came with VB (Package & Deployment wizard, iirc).  I use InnoSetup from
> http://www.jrsoftware.org/
> It is free, and in my opinion, hands down the best installer out there.
>
> Regards
>