Re: The difference between Reference and Component?

Ralph, does it mean that using COM as a component it is possible to have
more (or less) available controls (events) then when using it as a
reference?
Or the only difference is multiple COM Interfaces when using component?
Thanks,
Jack

"Ralph" <nt_consulting64@xxxxxxxxx> wrote in message
news:uY4h4i1MIHA.536@xxxxxxxxxxxxxxxxxxxxxxx

"Jack" <replyto@it> wrote in message
news:OyxcprvMIHA.4740@xxxxxxxxxxxxxxxxxxxxxxx
Hello,
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
dll,
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







.

Relevant Pages

  • Re: The difference between Reference and Component?
    ... Or the only difference is multiple COM Interfaces when using component? ... With any COM reference the IDE ... built-in Forms 'Designer' knows what to do with Controls when installed thru ...
    (microsoft.public.vb.general.discussion)
  • Re: implementing roles in OOP......
    ... > classes and interfaces contains no reference to public attributes - to ... OOPL code is that the OOPLs make some serious compromises with the ... >>represents a different business rule. ...
    (comp.object)
  • Re: implementing roles in OOP......
    ... focus on the areas that I understand/disagree/am becoming unsure of. ... classes and interfaces contains no reference to public attributes - to ... Not guilty - in fact my interfaces methods and state variables seem to ... immediately want to leverage this new paradigm, ...
    (comp.object)
  • Re: [patch] PCI Express Enhanced Config Patch - 2.6.0-test11
    ... To the Intel guess working out the ACPI 3.0 interfaces. ... How do we find the Root Complex Register Block? ... How does ACPI describe multiple MMCONFIG spaces? ...
    (Linux-Kernel)
  • Re: operator overloading
    ... but not divide - anything a mathematician would call a ring, ... Multipliable, Ring extends Addable, Multipliable, Dividable, Field extends ... If you provide an interface for each operator, obviously applications can define their own composite interfaces, but there may be places where the standard library uses multiple operators on a single type, so there might end up being some "standard" composite interfaces while other combinations of operators are unrepresented. ...
    (comp.lang.java.programmer)