How to write a COM components ...?

  • Thread starter Thread starter kathy
  • Start date Start date
K

kathy

In VB.NET help file "Walkthrough: Creating COM Objects
with Visual Basic .NET", It said:

"Note The COM objects you generate with Visual
Studio .NET cannot be used by other Visual Studio .NET
applications. Attempts to add references to such COM
objects raise an error."

My question is:

How to write a COM objects which can also be used by
Visual Studio .NET application?
 
"Note The COM objects you generate with Visual
Studio .NET cannot be used by other Visual Studio .NET
applications. Attempts to add references to such COM
objects raise an error."

My question is:

How to write a COM objects which can also be used by
Visual Studio .NET application?
Click to expand...

You notice that the Note above never says you cant reference the object
directly, you just can reference it as a COM object. So basically this mean
that when you create a .NET COM object, you get a .TLB file and a .DLL or
..EXE. The note above is just saying that you can't use the _COM_ object in
..NET, but the plain assembly (.DLL) should be fine.

This is the way I understood it, and I may be wrong, but does that make
sense?

~
Jeremy
 
kathy said:
In VB.NET help file "Walkthrough: Creating COM Objects
with Visual Basic .NET", It said:

"Note The COM objects you generate with Visual
Studio .NET cannot be used by other Visual Studio .NET
applications. Attempts to add references to such COM
objects raise an error."

My question is:

How to write a COM objects which can also be used by
Visual Studio .NET application?
Click to expand...

"Note The COM objects you generate with Visual
Studio .NET cannot be used by other Visual Studio .NET
applications. Attempts to add references to such COM
objects raise an error."


Maybe you could write a wrapper component in VB6 for your .NET COM component
and use it in the other .NET project... not really a good suggestion, I
know. Hopefully a better one: Do you really need a .NET-COM component in
another .NET application? Why don't you use the managed .NET component
directly, not via it's COM wrapper?
 
Hello,

kathy said:
In VB.NET help file "Walkthrough: Creating COM Objects
with Visual Basic .NET", It said:

"Note The COM objects you generate with Visual
Studio .NET cannot be used by other Visual Studio .NET
applications. Attempts to add references to such COM
objects raise an error."

My question is:

How to write a COM objects which can also be used by
Visual Studio .NET application?
Click to expand...

http://msdn.microsoft.com/library/en-us/vblr7/html/valrfCOMClassAttribute.asp

HTH,
Herfried K. Wagner
 
see my question and MSDN Note:
"Note The COM objects you generate with Visual
Studio .NET cannot be used by other Visual Studio .NET
applications. Attempts to add references to such COM
objects raise an error."
Click to expand...
 
Hello,

kathy said:
see my question and MSDN Note:
Click to expand...

My question: Why write a COM object in .NET for use with a .NET
application?!

Regards,
Herfried K. Wagner
 
¤ In VB.NET help file "Walkthrough: Creating COM Objects
¤ with Visual Basic .NET", It said:
¤
¤ "Note The COM objects you generate with Visual
¤ Studio .NET cannot be used by other Visual Studio .NET
¤ applications. Attempts to add references to such COM
¤ objects raise an error."
¤
¤ My question is:
¤
¤ How to write a COM objects which can also be used by
¤ Visual Studio .NET application?

The purpose of this article is to demonstrate how to build a .NET class for COM interop with
applications which implement COM (such as Visual Basic 6.0).

You don't need to build a COM class for use by .NET nor would you want to if you can build and use
standard .NET class libraries.


Paul ~~~ (e-mail address removed)
Microsoft MVP (Visual Basic)
 
The scenario could happen because I give the COM
component written in .NET which my custom might use it in
VB6 or .NET. I do not want to maintain different code
base.
 
kathy said:
The scenario could happen because I give the COM
component written in .NET which my custom might use it in
VB6 or .NET. I do not want to maintain different code
base.
Click to expand...

kathy, please read my reply to your orriginal post
 
Hello,

kathy said:
See my posting in this thread for your question.
;-)

then answer my question!
Click to expand...


The answer is simple: Reference the component as .NET component, not as a
COM object. You _cannot_ reference the COM object, but you can reference
the .NET component in your .NET applications.

Regards,
Herfried K. Wagner
 
Back
Top