"Bob Butler" <tiredofit@nospam.ever> wrote in message
news:OdbHNhbXHHA.4308@TK2MSFTNGP05.phx.gbl...
> "IVK" <Sumanth.***@gmail.com> wrote in message
> news:1172941699.967704.109450@z35g2000cwz.googlegroups.com
>> Hello,
>> I am having a project developed using VB 6.0. Now I have developed a
>> new project in VB 2005 and looking to using the dll's of the new
>> project in the already existing VB 6.0 project. Can I do this? can you
>> please provide the required details.
>
> You'd do better asking in a newsgroup with "dotnet" in the name; VB 2005
> is
> not the same language as VB 6 and is off-topic for this group.
>
> --
> Reply to the group so all can participate
> VB.Net: "Fool me once..."
>

On Mar 3, 5:54 pm, "Robert Morley" <rmor***@magma.ca.N0.Freak1n.sparn>
wrote:
> Yes, but he's incorporating it into a VB6 project, so either group makes
> sense, really.  Of course, historically speaking, those of mixed origins
> have often been rejected by both groups. :)
>
> Rob
>
> "Bob Butler" <tiredo...@nospam.ever> wrote in message
>
> news:OdbHNhbXHHA.4308@TK2MSFTNGP05.phx.gbl...
>
>
>
> > "IVK" <Sumanth.***@gmail.com> wrote in message
> >news:1172941699.967704.109450@z35g2000cwz.googlegroups.com
> >> Hello,
> >> I am having a project developed using VB 6.0. Now I have developed a
> >> new project in VB 2005 and looking to using the dll's of the new
> >> project in the already existing VB 6.0 project. Can I do this? can you
> >> please provide the required details.
>
> > You'd do better asking in a newsgroup with "dotnet" in the name; VB 2005
> > is
> > not the same language as VB 6 and is off-topic for this group.
>
> > --
> > Reply to the group so all can participate
> > VB.Net: "Fool me once..."- Hide quoted text -
>
> - Show quoted text -

> > OK. If I need to ask questions only related to VB 6.0,then here it
> > is ... I am looking for some VB 6.0 development tool which I can
> > download it from internet. Can anyone please suggest me a tool.
>
> There seems to be some annoyance in the tone of your response. I'm guessing
> you are not happy with being asked to go elsewhere with your question.
> However, since you have worked with both VB6 and VB2005 (according to your
> first post), then surely you must understand the large differences between
> the two languages. The people who frequent this newsgroup are, for the vast,
> vast majority, VB6 only programmers who have very, very little or no
> experience with the VB.NET world. Continuing to ask questions that
> incorporate VB.NET concepts here is likely to continue to be met with "blank
> stares" from us. On the other hand, the newsgroups you were directed to have
> lots of people who are experienced with both the VB6 and VB.NET worlds and
> are much more likely to be able to answer your question. The best advice you
> will receive here in this newsgroup is to ask your question(s) in a
> newsgroup devoted to the VB.NET programming languages. I'm sorry, but that
> is the reality of the situation.
>
> Rick

> ¤ > OK. If I need to ask questions only related to VB 6.0,then here it
> ¤ > is ... I am looking for some VB 6.0 development tool which I can
> ¤ > download it from internet. Can anyone please suggest me a tool.
> ¤
> ¤ There seems to be some annoyance in the tone of your response. I'm
> guessing
> ¤ you are not happy with being asked to go elsewhere with your question.
> ¤ However, since you have worked with both VB6 and VB2005 (according to
> your
> ¤ first post), then surely you must understand the large differences
> between
> ¤ the two languages. The people who frequent this newsgroup are, for the
> vast,
> ¤ vast majority, VB6 only programmers who have very, very little or no
> ¤ experience with the VB.NET world. Continuing to ask questions that
> ¤ incorporate VB.NET concepts here is likely to continue to be met with
> "blank
> ¤ stares" from us. On the other hand, the newsgroups you were directed to
> have
> ¤ lots of people who are experienced with both the VB6 and VB.NET worlds
> and
> ¤ are much more likely to be able to answer your question. The best advice
> you
> ¤ will receive here in this newsgroup is to ask your question(s) in a
> ¤ newsgroup devoted to the VB.NET programming languages. I'm sorry, but
> that
> ¤ is the reality of the situation.
>
> To be honest there are folks in both groups that use both, me being one of
> them.
>
> My suggestion is that if you (general) can't answer a question that
> involves the integration of the
> two perhaps not responding would be appropriate.

>> ¤ > OK. If I need to ask questions only related to VB 6.0,then here it
>> ¤ > is ... I am looking for some VB 6.0 development tool which I can
>> ¤ > download it from internet. Can anyone please suggest me a tool.
>> ¤
>> ¤ There seems to be some annoyance in the tone of your response. I'm
>> guessing
>> ¤ you are not happy with being asked to go elsewhere with your question.
>> ¤ However, since you have worked with both VB6 and VB2005 (according to
>> your
>> ¤ first post), then surely you must understand the large differences
>> between
>> ¤ the two languages. The people who frequent this newsgroup are, for the
>> vast,
>> ¤ vast majority, VB6 only programmers who have very, very little or no
>> ¤ experience with the VB.NET world. Continuing to ask questions that
>> ¤ incorporate VB.NET concepts here is likely to continue to be met with
>> "blank
>> ¤ stares" from us. On the other hand, the newsgroups you were directed to
>> have
>> ¤ lots of people who are experienced with both the VB6 and VB.NET worlds
>> and
>> ¤ are much more likely to be able to answer your question. The best advice
>> you
>> ¤ will receive here in this newsgroup is to ask your question(s) in a
>> ¤ newsgroup devoted to the VB.NET programming languages. I'm sorry, but
>> that
>> ¤ is the reality of the situation.
>>
>> To be honest there are folks in both groups that use both, me being one of
>> them.
>>
>> My suggestion is that if you (general) can't answer a question that
>> involves the integration of the
>> two perhaps not responding would be appropriate.
>
>I am going to guess that you missed my point completely. If a person is like
>you, a user of both products, then they attend both newsgroups; so, if a
>dotnet related product question were posted in the dotnet newsgroup, that
>person would see it and be able to respond to it there, right? For the
>VB-classic people in this newsgroup who do not use both products, questions
>involving the use of VB.NET or one of its successors is simply noise. Since
>the dotnet newsgroups were set up to handle questions about the dotnet
>product line, and since questions involving dotnet products will enjoy a
>readership made up of 100% similar users as opposed to a much, much smaller
>base of such readers here in this newsgroup (which was setup to handle
>questions about the classic versions of VB, by the way), why is it that you
>think I should not respond by trying to direct the dotnet'ers to where they
>have the best chance of getting an answer to their current question as well
>as any future ones?
>
>Rick
>

"Paul Clement" <UseAdddressAtEndofMess***@swspectrum.com> wrote in message
news:0cpou254qs849b990rc6i8gcbfufj752mq@4ax.com...
> On Mon, 05 Mar 2007 08:57:35 -0800, Stefan Berglund
> <sorry.no.kool***@for.me> wrote:
>
>
> ¤
> ¤ Attempting to use logic and reasoning on someone who understands neither
> ¤ will inevitably wind up being very frustrating.
>
> Perhaps you should consider that the frustration is a result of the
> failure in your own logic and
> reasoning.
>
> It might make you be a happier person. ;-)
>
>
> Paul
> ~~~~
> Microsoft MVP (Visual Basic)

> ¤ I am going to guess that you missed my point completely. If a person
> ¤ is like you, a user of both products, then they attend both newsgroups;
> ¤ so, if a dotnet related product question were posted in the dotnet
> ¤ newsgroup, that person would see it and be able to respond to it there,
> ¤ right? For the VB-classic people in this newsgroup who do not use both
> ¤ products, questions involving the use of VB.NET or one of its successors
> ¤ is simply noise. Since the dotnet newsgroups were set up to handle
> ¤ questions about the dotnet product line, and since questions involving
> ¤ dotnet products will enjoy a readership made up of 100% similar users
> ¤ as opposed to a much, much smaller base of such readers here in this
> ¤ newsgroup (which was setup to handle questions about the classic
> ¤ versions of VB, by the way), why is it that you think I should not
> respond
> ¤ by trying to direct the dotnet'ers to where they have the best chance of
> ¤ getting an answer to their current question as well as any future ones?
>
> That isn't the issue in this instance.

"Rick Rothstein (MVP - VB)" <rickNOSPAMnews@NOSPAMcomcast.net> wrote in
message news:eJvyc51XHHA.1216@TK2MSFTNGP03.phx.gbl...
|> ¤ I am going to guess that you missed my point completely. If a person
| > ¤ is like you, a user of both products, then they attend both
newsgroups;
| > ¤ so, if a dotnet related product question were posted in the dotnet
| > ¤ newsgroup, that person would see it and be able to respond to it
there,
| > ¤ right? For the VB-classic people in this newsgroup who do not use both
| > ¤ products, questions involving the use of VB.NET or one of its
successors
| > ¤ is simply noise. Since the dotnet newsgroups were set up to handle
| > ¤ questions about the dotnet product line, and since questions involving
| > ¤ dotnet products will enjoy a readership made up of 100% similar users
| > ¤ as opposed to a much, much smaller base of such readers here in this
| > ¤ newsgroup (which was setup to handle questions about the classic
| > ¤ versions of VB, by the way), why is it that you think I should not
| > respond
| > ¤ by trying to direct the dotnet'ers to where they have the best chance
of
| > ¤ getting an answer to their current question as well as any future
ones?
| >
| > That isn't the issue in this instance.
|
| Come on Paul, I **know** you are not as dense as you appear to be trying
to
| make me think you are.
|
| > The OP had asked how to use a VB.NET DLL from a Visual Basic 6.0 app.
| > The solution involves the integration of both products as documented in
| > the
| > MS KB article that I posted.
|
| Let's see if I can make this clearer for you. This newsgroup (as well as
| other with "vb" in their name, but without "dotnet" in there too) were
| created long before dotnet existed... it was set up so those using what is
| now known as the "classic" version of VB had a place to go to have their
| questions answered. If (try to follow this statement carefully)... if a
user
| **only** knows the classic version of VB, they will have **no** idea on
how
| to answer anything to do with the .NET version of VB, let alone one
dealing
| with how to integrate the two (interop.. what is that?). I can't believe
you
| would disagree with that, right? So, the only people here who could
possibly
| answer such questions are those who use VB.NET. Those people have their
| **own** newsgroups where such questions can and should be asked (those
with
| "dotnet" in their names). These are the **only** places where VB.NET
| questions should asked because... I'll repeat... those knowing **only**
the
| classic version of VB (frequenting the newsgroup that was set up for them
to
| post their questions to) won't have a clue as to how to use VB.NET,
whether
| by itself or integrated with VB6. I can't believe you would disagree with
| that statement either, right?
|
| > Most of those who use VB.NET no longer use Visual Basic 6.0 and many
| > have never used it.
|
| Those that have never used it... of course they can't answer the question
| any better than an VB-Classic only programmer can. Those who used to use
it,
| but who no longer do so.... well, maybe they might. But neither of these
| groups of people matter as they would not be visitors over in the VB
classic
| newsgroups either. BUT those whose actively use both version of VB, they
| could answer the question. I would not expect all of these people to be
| visitors in the VB classic newsgroups, but I would expect 100% of them to
| attend the VB.NET newsgroups (assuming they visit newsgroups at all). So,
| the best place for a question about VB.NET to get answered is **not** in a
| VB classic newsgroup. Wouldn't it make sense, then, for us here to direct
| people with VB.NET questions (whether about VB.NET alone or in conjunction
| with VB6) to the VB.NET newsgroups? And, I would follow that up with... it
| keeps the **noise** as low as possible over in the VB classic newsgroups
as
| a side benefit.
|
| > Do you think it would be fair of the VB.NET folks to punt him back to
the
| > Classic VB groups because they don't use Classic Visual Basic?
|
| I can't imagine why they even would consider doing that? As I said
earlier,
| if the question involves VB.NET, the only people who could possibly answer
| it are people who use VB.NET... period.
|
| > Given the nature of the upgrade path you have to expect crossover
| > questions
| > concerning interop and integration. Kicking them back and forth between
| > the
| > newsgroups will never help the user.
|
| No, I don't expect that at all (for the reasons I delineated above). Yes,
I
| expect errant questions from new VB.NET users who are unaware of the
| "dotnet" newsgroups; but I always respond to them with a message advising
| them of a better place to ask their questions. Seems like a logical thing
to
| do, no?
|
| Rick
|
|

"Kevin Provance" <ca***@tpasoft.com> wrote in message
news:OAGFEX4XHHA.3928@TK2MSFTNGP03.phx.gbl...
> Well, I suppose if anyone at MS who has anything to do with group creation
> ought to think about adding another group or two
>
> The obvious two that come to mind are:
>
> public.vb.vistacompatibility
> public.vb.dotnetcrossover
>
> We could then better organize some of these posts to a better suited
forum.
>
> But ya know...that's just one amateur's opinion.  ;-)
>

> wrote:
>
> ¤ > OK. If I need to ask questions only related to VB 6.0,then here it
> ¤ > is ... I am looking for some VB 6.0 development tool which I can
> ¤ > download it from internet. Can anyone please suggest me a tool.
> ¤
> ¤ There seems to be some annoyance in the tone of your response. I'm
guessing
> ¤ you are not happy with being asked to go elsewhere with your question.
> ¤ However, since you have worked with both VB6 and VB2005 (according to
your
> ¤ first post), then surely you must understand the large differences
between
> ¤ the two languages. The people who frequent this newsgroup are, for the
vast,
> ¤ vast majority, VB6 only programmers who have very, very little or no
> ¤ experience with the VB.NET world. Continuing to ask questions that
> ¤ incorporate VB.NET concepts here is likely to continue to be met with
"blank
> ¤ stares" from us. On the other hand, the newsgroups you were directed to
have
> ¤ lots of people who are experienced with both the VB6 and VB.NET worlds
and
> ¤ are much more likely to be able to answer your question. The best advice
you
> ¤ will receive here in this newsgroup is to ask your question(s) in a
> ¤ newsgroup devoted to the VB.NET programming languages. I'm sorry, but
that
> ¤ is the reality of the situation.
>
> To be honest there are folks in both groups that use both, me being one of
them.
>
> My suggestion is that if you (general) can't answer a question that

"Bob Butler" <tiredofit@nospam.ever> wrote in message
news:eJkiFlfXHHA.2448@TK2MSFTNGP02.phx.gbl...
> "Robert Morley" <rmor***@magma.ca.N0.Freak1n.sparn> wrote in message
> news:ObFkB0bXHHA.2320@TK2MSFTNGP03.phx.gbl
>> Yes, but he's incorporating it into a VB6 project, so either group
>> makes sense, really.
>
> I considered that but the problem in this case is to create the dotnet DLL
> such that it exposes the COM interface for VB6 to use.  There's nothing to
> be done on the VB6 side except wait for the dotnet options to be set
> appropriately.  How to do that is a topic for the dotnetters to respond
> to.
>
> --
> Reply to the group so all can participate
> VB.Net: "Fool me once..."
>

"IVK" <Sumanth.***@gmail.com> wrote in message
news:1172941699.967704.109450@z35g2000cwz.googlegroups.com...
> Hello,
> I am having a project developed using VB 6.0. Now I have developed a
> new project in VB 2005 and looking to using the dll's of the new
> project in the already existing VB 6.0 project. Can I do this? can you
> please provide the required details.
>