Project references to Type library (.tlb) files


DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 11 of 11

Thread: Project references to Type library (.tlb) files

  1. #1
    Heather B. Guest

    Project references to Type library (.tlb) files


    Hi there,

    Does a .tlb file need you ship with an app? I've always thought so, but
    recently I accidentally shipped an app without a heavily used .tlb, that I
    confirmed was not on any target machine, and the app ran without problems
    entirely. That shocked me. Then I remembered hearing that the .tlb
    information is used at design time for auto-list members, and at compile
    time to compute function pointers

    Can someone help me out here to understand this?

    Any references you can point me to learn more about this stuff?

    Thanks,
    Heather




  2. #2
    Heather B. Guest

    Re: Project references to Type library (.tlb) files


    Sorry - English IS my first language - I'm just not good at proof reading my
    own posts. The question was supposed to be: Does a .tlb file referenced in
    Project|References need to be shipped with an app?


    "Heather B." <heatherb@NOSPAM.attglobal.net> wrote in message
    news:3afb25d6$1@news.devx.com...
    >
    > Hi there,
    >
    > Does a .tlb file need you ship with an app? I've always thought so, but
    > recently I accidentally shipped an app without a heavily used .tlb, that I
    > confirmed was not on any target machine, and the app ran without problems
    > entirely. That shocked me. Then I remembered hearing that the .tlb
    > information is used at design time for auto-list members, and at compile
    > time to compute function pointers
    >
    > Can someone help me out here to understand this?
    >
    > Any references you can point me to learn more about this stuff?
    >
    > Thanks,
    > Heather
    >
    >
    >




  3. #3
    Heather B. Guest

    Re: Project references to Type library (.tlb) files


    Sorry - English IS my first language - I'm just not good at proof reading my
    own posts. The question was supposed to be: Does a .tlb file referenced in
    Project|References need to be shipped with an app?


    "Heather B." <heatherb@NOSPAM.attglobal.net> wrote in message
    news:3afb25d6$1@news.devx.com...
    >
    > Hi there,
    >
    > Does a .tlb file need you ship with an app? I've always thought so, but
    > recently I accidentally shipped an app without a heavily used .tlb, that I
    > confirmed was not on any target machine, and the app ran without problems
    > entirely. That shocked me. Then I remembered hearing that the .tlb
    > information is used at design time for auto-list members, and at compile
    > time to compute function pointers
    >
    > Can someone help me out here to understand this?
    >
    > Any references you can point me to learn more about this stuff?
    >
    > Thanks,
    > Heather
    >
    >
    >




  4. #4
    ravi Guest

    Re: Project references to Type library (.tlb) files


    Hi,
    In case of VB component there are two files created *.tlb and *.vbr. If
    you have sent *.vbr along with the app then the app will be working even
    without *.tlb. Check if you have sent *.vbr file along with the app.
    cheers,
    Ravi.
    "Heather B." <heatherb@NOSPAM.attglobal.net> wrote:
    >
    >Sorry - English IS my first language - I'm just not good at proof reading

    my
    >own posts. The question was supposed to be: Does a .tlb file referenced

    in
    >Project|References need to be shipped with an app?
    >
    >
    >"Heather B." <heatherb@NOSPAM.attglobal.net> wrote in message
    >news:3afb25d6$1@news.devx.com...
    >>
    >> Hi there,
    >>
    >> Does a .tlb file need you ship with an app? I've always thought so, but
    >> recently I accidentally shipped an app without a heavily used .tlb, that

    I
    >> confirmed was not on any target machine, and the app ran without problems
    >> entirely. That shocked me. Then I remembered hearing that the .tlb
    >> information is used at design time for auto-list members, and at compile
    >> time to compute function pointers
    >>
    >> Can someone help me out here to understand this?
    >>
    >> Any references you can point me to learn more about this stuff?
    >>
    >> Thanks,
    >> Heather
    >>
    >>
    >>

    >
    >



  5. #5
    ravi Guest

    Re: Project references to Type library (.tlb) files


    Hi,
    In case of VB component there are two files created *.tlb and *.vbr. If
    you have sent *.vbr along with the app then the app will be working even
    without *.tlb. Check if you have sent *.vbr file along with the app.
    cheers,
    Ravi.
    "Heather B." <heatherb@NOSPAM.attglobal.net> wrote:
    >
    >Sorry - English IS my first language - I'm just not good at proof reading

    my
    >own posts. The question was supposed to be: Does a .tlb file referenced

    in
    >Project|References need to be shipped with an app?
    >
    >
    >"Heather B." <heatherb@NOSPAM.attglobal.net> wrote in message
    >news:3afb25d6$1@news.devx.com...
    >>
    >> Hi there,
    >>
    >> Does a .tlb file need you ship with an app? I've always thought so, but
    >> recently I accidentally shipped an app without a heavily used .tlb, that

    I
    >> confirmed was not on any target machine, and the app ran without problems
    >> entirely. That shocked me. Then I remembered hearing that the .tlb
    >> information is used at design time for auto-list members, and at compile
    >> time to compute function pointers
    >>
    >> Can someone help me out here to understand this?
    >>
    >> Any references you can point me to learn more about this stuff?
    >>
    >> Thanks,
    >> Heather
    >>
    >>
    >>

    >
    >



  6. #6
    Warren Galyen Guest

    Re: Project references to Type library (.tlb) files

    Type libraries are only required before compiling a project. Whatever
    functions you reference from the type lib are compiled into your program
    when you create an executable and so the type lib is longer required to run
    the program.

    "Heather B." <heatherb@NOSPAM.attglobal.net> wrote in message
    news:3afb25d6$1@news.devx.com...
    >
    > Hi there,
    >
    > Does a .tlb file need you ship with an app? I've always thought so, but
    > recently I accidentally shipped an app without a heavily used .tlb, that I
    > confirmed was not on any target machine, and the app ran without problems
    > entirely. That shocked me. Then I remembered hearing that the .tlb
    > information is used at design time for auto-list members, and at compile
    > time to compute function pointers
    >
    > Can someone help me out here to understand this?
    >
    > Any references you can point me to learn more about this stuff?
    >
    > Thanks,
    > Heather
    >
    >
    >




  7. #7
    Warren Galyen Guest

    Re: Project references to Type library (.tlb) files

    Type libraries are only required before compiling a project. Whatever
    functions you reference from the type lib are compiled into your program
    when you create an executable and so the type lib is longer required to run
    the program.

    "Heather B." <heatherb@NOSPAM.attglobal.net> wrote in message
    news:3afb25d6$1@news.devx.com...
    >
    > Hi there,
    >
    > Does a .tlb file need you ship with an app? I've always thought so, but
    > recently I accidentally shipped an app without a heavily used .tlb, that I
    > confirmed was not on any target machine, and the app ran without problems
    > entirely. That shocked me. Then I remembered hearing that the .tlb
    > information is used at design time for auto-list members, and at compile
    > time to compute function pointers
    >
    > Can someone help me out here to understand this?
    >
    > Any references you can point me to learn more about this stuff?
    >
    > Thanks,
    > Heather
    >
    >
    >




  8. #8
    Michael Shutt Guest

    Re: Project references to Type library (.tlb) files

    Although your application may not need it for local components, I think you
    would need to distribute the tlb for remote (dcom) components so that COM
    can do the marshalling (since it would have to look up the interface
    definitions).

    --
    Michael Shutt

    Please respond to newsgroup as I will not return direct emails.

    "Heather B." <heatherb@NOSPAM.attglobal.net> wrote in message
    news:3afb25d6$1@news.devx.com...
    >
    > Hi there,
    >
    > Does a .tlb file need you ship with an app? I've always thought so, but
    > recently I accidentally shipped an app without a heavily used .tlb, that I
    > confirmed was not on any target machine, and the app ran without problems
    > entirely. That shocked me. Then I remembered hearing that the .tlb
    > information is used at design time for auto-list members, and at compile
    > time to compute function pointers
    >
    > Can someone help me out here to understand this?
    >
    > Any references you can point me to learn more about this stuff?
    >
    > Thanks,
    > Heather
    >
    >
    >




  9. #9
    Michael Shutt Guest

    Re: Project references to Type library (.tlb) files

    Although your application may not need it for local components, I think you
    would need to distribute the tlb for remote (dcom) components so that COM
    can do the marshalling (since it would have to look up the interface
    definitions).

    --
    Michael Shutt

    Please respond to newsgroup as I will not return direct emails.

    "Heather B." <heatherb@NOSPAM.attglobal.net> wrote in message
    news:3afb25d6$1@news.devx.com...
    >
    > Hi there,
    >
    > Does a .tlb file need you ship with an app? I've always thought so, but
    > recently I accidentally shipped an app without a heavily used .tlb, that I
    > confirmed was not on any target machine, and the app ran without problems
    > entirely. That shocked me. Then I remembered hearing that the .tlb
    > information is used at design time for auto-list members, and at compile
    > time to compute function pointers
    >
    > Can someone help me out here to understand this?
    >
    > Any references you can point me to learn more about this stuff?
    >
    > Thanks,
    > Heather
    >
    >
    >




  10. #10
    Paul Clement Guest

    Re: Project references to Type library (.tlb) files

    On Thu, 10 May 2001 16:42:02 -0700, "Heather B." <heatherb@NOSPAM.attglobal.net> wrote:


    Hi there,

    Does a .tlb file need you ship with an app? I've always thought so, but
    recently I accidentally shipped an app without a heavily used .tlb, that I
    confirmed was not on any target machine, and the app ran without problems
    entirely. That shocked me. Then I remembered hearing that the .tlb
    information is used at design time for auto-list members, and at compile
    time to compute function pointers

    Can someone help me out here to understand this?

    Any references you can point me to learn more about this stuff?

    Thanks,
    Heather

    If the type library is from a dependent component you use in your application/component the answer
    is 'no'.

    If you are developing an ActiveX (or COM) component, the type library for your component in stored
    internally.

    You can create an external type library file for your component. This is useful for providing the
    development features (such as Intellisense, etc) for environments where the component is not
    installed - like when developing ASP pages in InterDev. It is also used for registering a component
    on a client machine when using the distributed component object model (DCOM) where the component
    resides on a remote machine.


    Paul ~~~ pclement@ameritech.net
    Microsoft MVP (Visual Basic)

  11. #11
    Paul Clement Guest

    Re: Project references to Type library (.tlb) files

    On Thu, 10 May 2001 16:42:02 -0700, "Heather B." <heatherb@NOSPAM.attglobal.net> wrote:


    Hi there,

    Does a .tlb file need you ship with an app? I've always thought so, but
    recently I accidentally shipped an app without a heavily used .tlb, that I
    confirmed was not on any target machine, and the app ran without problems
    entirely. That shocked me. Then I remembered hearing that the .tlb
    information is used at design time for auto-list members, and at compile
    time to compute function pointers

    Can someone help me out here to understand this?

    Any references you can point me to learn more about this stuff?

    Thanks,
    Heather

    If the type library is from a dependent component you use in your application/component the answer
    is 'no'.

    If you are developing an ActiveX (or COM) component, the type library for your component in stored
    internally.

    You can create an external type library file for your component. This is useful for providing the
    development features (such as Intellisense, etc) for environments where the component is not
    installed - like when developing ASP pages in InterDev. It is also used for registering a component
    on a client machine when using the distributed component object model (DCOM) where the component
    resides on a remote machine.


    Paul ~~~ pclement@ameritech.net
    Microsoft MVP (Visual Basic)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center