Re: The difference between Reference and Component?
- From: "Ralph" <nt_consulting64@xxxxxxxxx>
- Date: Fri, 30 Nov 2007 07:55:36 -0600
"Jack" <replyto@it> wrote in message
news:OyxcprvMIHA.4740@xxxxxxxxxxxxxxxxxxxxxxx
Hello,dll,
My project is using dll (COM object) which is listed under References.
It works fine.
But, accidently when browsing the Components list I have found the same
listed under the same name but it is not selected (not checked).
I wonder, should that COM be used as a component or reference or both?
How to know? What can be a difference?
Your thoughts please,
Jack
Any COM component can provide implementation for multiple COM Interfaces.
Any component can also supply multiple controls, as well as mulitple
Interfaces. Thus no one component is necessary just a "Reference",
"Control", or "Designer", or ...
In general when VB loads the References list it merely reads the Registry
for those Interfaces that describe a typelibrary. When loading the
Components dialog it looks for those that describe themselves in the
Registry as "Controls" or "Insertable". "Designers" go through a similar
process with another level of indirection.
Also note just because you can "see" a component's interface in the Project
References or Components dialog doesn't necessary mean you can use it
successfully within your project. For example, the DataEnvironment component
msde (?) shows a Reference for the DE interface, but this interface is only
used by VB's internal designer manager.
hth
-ralph
.
- Follow-Ups:
- References:
- Prev by Date: Re: How to copy only the contents of a picturebox?
- Next by Date: Re: How to copy only the contents of a picturebox?
- Previous by thread: Re: The difference between Reference and Component?
- Next by thread: Re: The difference between Reference and Component?
- Index(es):
Relevant Pages
|
