A page on doing
(versions up to 6, but not VB.NET, version 7).
has better features such as true inheritance, but people still have to work with legacy programs.
A good book on Component Development for
Developing COM/ActiveX Components with Visual Basic 6
by Dan Appleman.
I put this book up here as well:
Visual Basic 6 COM+ Programming Bible
by John Paul Mueller.
, are they all very confusing to Mainframe developers having to work with Objects? Not if the
ive is to stay employed.
In the case of
VbClassic, the objects are always accessed via a particular model, e.g. the ComponentObjectModel (COM). So one could say that the distinction does not actually arise. Of course, the important thing is to define what one means by a "component".
Another Interesting thing to note is that
example. -- dl
See three VbClassicSupportForXmlProcessing, XmlRpc and RSS examples
with impressive release notes, install and help, think suitable for beginners
Applications of Com objects created via
for beginners in Com technology
The next one looked advanced to me and is C based, but I put it up anyway
days, people started to talk about
. One company's view on what that means for
is described at
VbClassic pages to be checked out Refactoring:
Wiki OO pages to be checked out
of this page
(last edited EditText February 13, 2009)
or FindPage with title or text search