Thanks Tim, that gives me a great idea, maybe trying to find documentation
and examples of the first release and see how it was presented. That book
looks excellent, my library system doesnt have it, neither is it close by in
the UC library system. I will put this book into my search/wish list.
The Amazon search also pulled up other books (those who bought...).
And yes, the documentation does seem geared to developers who have been
using it. I was feeling kind of dumb not grasping some of the stuff.
Since dotnet is going to be widely used it seems to me folks will be
migrating up or across from COM. Here Ive been hoping to find ways to
insert machine code into C# source to make it easier but maybe I should just
learn how you all are using the dotnet platform.
Are you familiar with Labview
www.ni.com ? When I hear that some
application code calls an object to do a function, it reminds me of a vi;
You create one vi to handle a com port or parse data or display data, save
it, then other apps can reference it, saving time. Sort of like a semi
independent module of code where you only interact with its interfaces, and
dont care how it works.
"Tim S." <Ti**@discussions.microsoft.com> wrote in message
news:36**********************************@microsof t.com...
Honestly you are very late in the game. But this shows you have spirit.
I imagine most online COM/COM+ documentation is geared to the 99% developers
who have been programming in it for years.
I suggest getting a good beginner book.
You might find the following title helpful:
The COM and COM+ Programming Primer by Alan Gordon
You may have to buy it used at Amazon.com. Or you could just wing by
studying .Net. The .Net interoop documentation should be able to show you
all you need to know.
Good Luck
"Bradley1234" wrote:
Hi
Im trying to really understand COM and the replacement in the newer .net
framework.
Coming from an embedded side and not riding the Windows wave in the 90s,
COM seems difficult to grasp. The msdn library documentation seems to go in
circles, saying: what is com? well its, its sort of like, com is, whats
com? its extensible, its versatile, for a better description click <here>.
So that click brings up another page, com is unique, its powerful, its made
for you, for a better description, click <here> (which is the page you
came from.)
If comparing COM to LabView, would a COM object be like a .vi ?
Where you simply bring in the .vi and connect up the interfaces?
Im running a C# Express Beta (which is awesome) and want to try COM or
COM+, is this possible?
Is ActiveX a similar thing? Its like this hidden thing, hard to
understand, is there a design wizard to help create an AX component?
mtia
