VB7 and COM

[Marc D'Aoust]

I've always considered VB to be a COM RAD tool. But with the announcement
that VB7 will support inheritance and other pure object features I have a
serious question about how much of a RAD tool it will be. COM doesn't
support inheritance, neither does COM+ (as far as I know so far). Which
means that standard classes will probably no longer be COM compliant. So how
are we going to create COM classes. Will we have an ATL style of development
with templates and separately defined interfaces. While I do like the
concept of defining my interface separately, I don't think the average RAD
programmer wants, or cares, to learn IDL. Then maybe some sort of wizard
interface to generate and manage the interfaces? **** why not make the
system extendable and make a plug-in for developing CORBA objects in VB
(CORBA supports inheritance right?).

Microsoft did say that we are not going to be able port VB5/6 projects
directly to VB7. This is probably one of the reasons. VB5/6 transparently
permeates COM in almost everything it does.

Will it still qualify as a COM RAD tool? Can the average corporate developer
handle object oriented programming? I have seen many examples of pure
spaghetti developed in Powerbuilder because inheritance was used carelessly.
These features may just be a Gideon's Sword.

Well, does anybody have any info on this ??

Let me know.

Marc D'Aoust
Senior Systems Architect / Director Of Research and Development

[Michael \(michka\) Kaplan]

I think you are assuming WAY too much here, especially given the fact that
COM+ is not a static technology and it has the same year to grow that VB7
does.

--
?MichKa
(insensitive fruitarian)

random junk of dubious value, a multilingual website, the
54-language TSI Form/Report to Data Access Page Wizard,
and lots of replication "stuff" at the (no scripts required!)
http://www.trigeminal.com/

?
"Marc D'Aoust" <marc_daoust@hotmail.com> wrote in message
news:38cddfbe@news.devx.com...
> I've always considered VB to be a COM RAD tool. But with the announcement
> that VB7 will support inheritance and other pure object features I have a
> serious question about how much of a RAD tool it will be. COM doesn't
> support inheritance, neither does COM+ (as far as I know so far). Which
> means that standard classes will probably no longer be COM compliant. So
how
> are we going to create COM classes. Will we have an ATL style of
development
> with templates and separately defined interfaces. While I do like the
> concept of defining my interface separately, I don't think the average RAD
> programmer wants, or cares, to learn IDL. Then maybe some sort of wizard
> interface to generate and manage the interfaces? **** why not make the
> system extendable and make a plug-in for developing CORBA objects in VB
> (CORBA supports inheritance right?).
>
> Microsoft did say that we are not going to be able port VB5/6 projects
> directly to VB7. This is probably one of the reasons. VB5/6 transparently
> permeates COM in almost everything it does.
>
> Will it still qualify as a COM RAD tool? Can the average corporate
developer
> handle object oriented programming? I have seen many examples of pure
> spaghetti developed in Powerbuilder because inheritance was used
carelessly.
> These features may just be a Gideon's Sword.
>
> Well, does anybody have any info on this ??
>
> Let me know.
>
> Marc D'Aoust
> Senior Systems Architect / Director Of Research and Development
>
>