>
>> >
>> I don't know what Spy++ is.  I looked in the Object Browser and the COM
>> section of Add Reference, but couldn't find "Program Manager" or desktop.
> I
>> also looked through MSDN.
>>
>> And in general, I know very little about VB.  Mostly I use C++.  VB has
>> access to some things that are hard to get to with C++ -- but only if I
> can
>> find out where they are in VB.
>>
>
>   Do you mean VB or VB.Net? Your question from
> a few days ago was regarding VB.Net, which has
> a different newsgroup. (And you never made it clear
> in your last thread that you understood that.)
>
>

"Tom Shelton" <tom_shel***@comcastXXXXXXX.net> wrote in message
news:eomyTT3kJHA.4252@TK2MSFTNGP02.phx.gbl...

>>> Most likely you're correct.  The COM section of add reference is a dead
>>> give away :)  There is no other kind of reference in VB6's reference
>>> dialog :)
>>>
>>
>>   Yes. And he doesn't know what Spy++ is. It's
>> hard to imagine how he could have gone through
>> all of that discussion and arguing in his last post
>> and still not grok that he's in the wrong group!
>
> Not knowing what Spy++ is is not an indicator either way.  I've known lots
> of
> VB programmers over the years that had no idea what it was either.

> "Tom Shelton" <tom_shel***@comcastXXXXXXX.net> wrote in message
> news:eomyTT3kJHA.4252@TK2MSFTNGP02.phx.gbl...
>
>>>> Most likely you're correct.  The COM section of add reference is a dead
>>>> give away :)  There is no other kind of reference in VB6's reference
>>>> dialog :)
>>>>
>>>
>>>   Yes. And he doesn't know what Spy++ is. It's
>>> hard to imagine how he could have gone through
>>> all of that discussion and arguing in his last post
>>> and still not grok that he's in the wrong group!
>>
>> Not knowing what Spy++ is is not an indicator either way.  I've known lots
>> of
>> VB programmers over the years that had no idea what it was either.
>
> Do you even get Spy++ with the basic VB installation? I thought you only got
> it if you had the full VS6. (I.e., I'm with you: I wouldn't use knowledge of
> that program to distinguish between a VB6'er and a .NET'er.)

>
> "Karl E. Peterson" <k***@mvps.org> wrote in message
> news:uc$dKH6kJHA.1248@TK2MSFTNGP03.phx.gbl...
>| Oughta be.  I don't have an ISO of my Pro disc handy, but try looking in
> the same
>| folder I pointed to earlier (\Common\Tools\VB\spy\), or just do a filename
> search
>| (spyxx.exe).
>
> I have the VB6 Pro CD, and it's there.  And to throw in another voice, it
> *is* single handedly the most useful tool I've worked with for cross task
> programming.
>
>

"Tom Shelton" <tom_shel***@comcastXXXXXXX.net> escribió en el mensaje
news:uCNdWAwkJHA.3760@TK2MSFTNGP03.phx.gbl...
> On 2009-02-19, mayayana <mayayaX***@rcXXn.com> wrote:
>>
>>> >
>>> I don't know what Spy++ is.  I looked in the Object Browser and the COM
>>> section of Add Reference, but couldn't find "Program Manager" or
>>> desktop.
>> I
>>> also looked through MSDN.
>>>
>>> And in general, I know very little about VB.  Mostly I use C++.  VB has
>>> access to some things that are hard to get to with C++ -- but only if I
>> can
>>> find out where they are in VB.
>>>
>>
>>   Do you mean VB or VB.Net? Your question from
>> a few days ago was regarding VB.Net, which has
>> a different newsgroup. (And you never made it clear
>> in your last thread that you understood that.)
>>
>>
>
> Most likely you're correct.  The COM section of add reference is a dead
> give
> away :)  There is no other kind of reference in VB6's reference dialog :)
>
> --
> Tom Shelton

"mayayana" <mayayaX***@rcXXn.com> wrote in message
news:ux%23Jt1ukJHA.500@TK2MSFTNGP06.phx.gbl...
>
>> >
>> I don't know what Spy++ is.  I looked in the Object Browser and the COM
>> section of Add Reference, but couldn't find "Program Manager" or desktop.
> I
>> also looked through MSDN.
>>
>> And in general, I know very little about VB.  Mostly I use C++.  VB has
>> access to some things that are hard to get to with C++ -- but only if I
> can
>> find out where they are in VB.
>>
>
>  Do you mean VB or VB.Net? Your question from
> a few days ago was regarding VB.Net, which has
> a different newsgroup. (And you never made it clear
> in your last thread that you understood that.)
>
>

"Bill McCarthy" <I Are Identity Thieves> wrote in message
news:Ojz0k8UlJHA.5980@TK2MSFTNGP06.phx.gbl...
|
| "mayayana" <mayayaX***@rcXXn.com> wrote in message
| news:eaVVAy2kJHA.4028@TK2MSFTNGP03.phx.gbl...
| >
| >   There are some strong feelings around .Net. A lot
| > of VB people are unhappy that MS just dropped VB.
|
| They didn't. VB is alive and well.
|
| > And there are .Net people who like to hang around here
| > and basically say, "When are you people going to stop
| > complaining
|
|
| And when are you going to stop posting falsehoods and unwarranted attacks
?
|
|
| >
| >   As you can imagine, that's a volatile mix. :)  So accidental
| > .Net posts here often get answered by sarcastic digs.
|
| And in particualr you posting incorrect and misleading information, which
| then has to be corrected.  If it was truly .NET trolls starting things
then
| I'd imagine they would post abotu all the goodness .NET has to offer...
hmmm
| there's an idea....  <eg>
|
|
|
| >
| >   In about 2001 MS introduced .Net, which was their
| > answer to Java. It's a JIT-compiled OO system that runs
| > on top of a large virtual machine known as the .Net Framework.
|
| LOL.  Please stick to talking about things you know about.  To think the
| .NET runtime is the same as the .NEt framework is ludicrous.  The .NEt
| runtime, often referred to as the CLR (Common Language Runtime) is the
| *runtime* that managed the VM.  The .NEt Framework is a rich set of
| libraries that are readily accessible to .NEt developers as well of course
| as activeX and unmanaged C exports.
|
|
| >
| >   As I explained in the earlier post, VB.Net has been saddled
| > with a dizzying collection of version names and numbers, and
| > as with most Microsoft versioning, it's more marketing than
| > anything else. But the gist of it is that VB 5,6 are VB and just
| > about anything else you see is VB.Net 7,8,9,2003,2005,2008,
| > 1.1,2,3, etc. Tom Shelton laid out the details of what's what
| > with the .Net versions in the earlier thread.
| >
|
| Both Tom and I have told you the correct names and version numbers time
| after time, yet you continually post wrong numbers.  why is that ?  Trying
| to start an arguement or something ?
|
|
| There is no VB.NEt 1.1, 2 or 3, it is VB7 (2002), VB7.1 (2003), VB8 (2005)
| and VB9 (2008). In VB7 and 7.1 the ".NET" name was oftne added to make it
| clear to folks that VB had moved to the .NEt platform.
|
|
| > As for COM:
| >  From what I've seen VB is far more well adapted to COM
| > than is C++, but I don't know about VB.Net.
|
| Yes you clealry don't.
|
| > .Net is not
| > really aimed at writing Windows software, thus the .Net
| > worldview views COM as "legacy".
|
| What complete and utter nonsense.  .NET is aimed at writing Windows
software
| and does so with more compliancy than VB6.  I suggest rather than starting
| that argument in here, you limit yourself to things you do know about,
which
| for you as you stated above, does not include .NET
|
|
|
|
|
|
|
|
|
|
|
|
|

"Cor Ligthert[MVP]" <Notmyfirstn***@planet.nl> wrote in message
news:%23Chd8GalJHA.1248@TK2MSFTNGP03.phx.gbl...
| Bill,
|
| >
| > There is no VB.NEt 1.1, 2 or 3, it is VB7 (2002), VB7.1 (2003), VB8
(2005)
| > and VB9 (2008). In VB7 and 7.1 the ".NET" name was oftne added to make
it
| > clear to folks that VB had moved to the .NEt platform.
| >
|
| You often have written this and in my opinion it is not true.
| I have written this often to you and I have to admit that I also was first
| wrong in my understanding of this.
| However, you have showed me clearly that there is a language version and a
| product version.
|
| I have always tried to point me on the product in the way as it sold by
| Microsoft, which was :
| ..starting at what is in this newsgroup often called Visual Basic Classic
| Visual Studio 98 (contains Visual Basic6), while there were also some
other
| versions beside Visual Studio 98
| Visual Studio 2002 (contains VB.Net 2002), while there was also a Standard
| VB version sold (to compare with the now free VB Express).
| Visual Studio 2003 (contains VB.Net 2003)
| Visual Studio 2005 (contains VB 2005) plus an express version
| Visual Studio 2008 (contains VB 2008) plus an express version
|
| However, the program language itself has had only slight changes
(extended)
|
| The products itself has changed where after VB6 by instance some Com
| controls are disapeared (placed in a kind of VisualBasicCompatable
| namespace) or got minor changes, however some people see controls and
things
| like that as parts of the language)
| The Visual Basic Compatible namespace should not be confused with the
| Microsoft VisualBasic namespace, which is and will stay a full part of the
| Net framework beside the basic System.Net namespace.
|
| The VB Languages versions of the last 11 years are
| VB6 latest version based on Com
| VB7 first version based on Net and made VB perform in the same speed as by
| instance C#. VB7 came with a rich set of classes with their members, which
| by some people will be confused with the language.
| VB 7.1 (in VS 2003), in fact the first very stable version, it had minor
| (very usable) changes in the language
| VB 8 (in VS 2005), with by instance the "My" class, not liked by straight
| OOP developers, but mainly very good to fill the gab between VB6 behaviour
| and the Net way of that.
| VB 9 (in VS 2008), introducing Linq however more of that.  By instance a
| DataContext which is a little bit more like the typical from the days of
VB6
| recordset.
|
| Cor
|

>
> "mayayana" <mayayaX***@rcXXn.com> wrote in message
> news:ux%23Jt1ukJHA.500@TK2MSFTNGP06.phx.gbl...
>>
>>> >
>>> I don't know what Spy++ is.  I looked in the Object Browser and the COM
>>> section of Add Reference, but couldn't find "Program Manager" or desktop.
>> I
>>> also looked through MSDN.
>>>
>>> And in general, I know very little about VB.  Mostly I use C++.  VB has
>>> access to some things that are hard to get to with C++ -- but only if I
>> can
>>> find out where they are in VB.
>>>
>>
>>  Do you mean VB or VB.Net? Your question from
>> a few days ago was regarding VB.Net, which has
>> a different newsgroup. (And you never made it clear
>> in your last thread that you understood that.)
>>
>>
> I am using VB 2008 Express.  I know nothing about VB and VB.Net.  How would
> I find out which I'm using?  If it's relevant, the "Add Reference" dialog
> has a .NET tab and a COM tab.  You're right, I didn't understand the long
> debate that went on after my last question.  It was a very emotional debate,
> and I couldn't tell when people were being straightforward -- sometimes it
> seemed like they were being sarcastic.  In any case, someone did answer my
> last poorly-expressed question, and I've gotten both a console app and a
> Windows app to run.  Maybe I'll soon get the hang of this VB.whateveritis
> after all.   :)
>
> So, is this the right newsgroup for whatever VB I'm using?  If it isn't,
> what is?