Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. IT & Infrastructure
  4. Using multiple source dispinterfaces with VB

Using multiple source dispinterfaces with VB

Scheduled Pinned Locked Moved IT & Infrastructure
question
4 Posts 1 Posters 14 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • L Offline
    L Offline
    Lost User
    wrote on last edited by
    #1

    I have an ATL3 object that is used by a VB6 client. My object supports two interfaces, one of them is an outgoing (event) dispinterface. Everything is ok so far, but when I add a second outgoing dispinterface VB doesn't see it. What do I need to do so my objects can support several different outgoing dispinterfaces? coclass MyCoClass { [default] interface IMyInterface; [default, source] dispinterface DIMyEvents1; [source] dispinterface DIMyEvents2; // VB doesn't see this! };

    L 1 Reply Last reply
    0
    • L Lost User

      I have an ATL3 object that is used by a VB6 client. My object supports two interfaces, one of them is an outgoing (event) dispinterface. Everything is ok so far, but when I add a second outgoing dispinterface VB doesn't see it. What do I need to do so my objects can support several different outgoing dispinterfaces? coclass MyCoClass { [default] interface IMyInterface; [default, source] dispinterface DIMyEvents1; [source] dispinterface DIMyEvents2; // VB doesn't see this! };

      L Offline
      L Offline
      Lost User
      wrote on last edited by
      #2

      The "Visual Programmer" article in this months MSJ looks like just what you need - he describes getting events from the non-default source interface. ================== The original message was: I have an ATL3 object that is used by a VB6 client. My object supports two interfaces, one of them is an outgoing (event) dispinterface. Everything is ok so far, but when I add a second outgoing dispinterface VB doesn't see it. What do I need to do so my objects can support several different outgoing dispinterfaces?

      coclass MyCoClass
      {
      [default] interface IMyInterface;
      [default, source] dispinterface DIMyEvents1;
      [source] dispinterface DIMyEvents2; // VB doesn't see this!
      };

      L 1 Reply Last reply
      0
      • L Lost User

        The "Visual Programmer" article in this months MSJ looks like just what you need - he describes getting events from the non-default source interface. ================== The original message was: I have an ATL3 object that is used by a VB6 client. My object supports two interfaces, one of them is an outgoing (event) dispinterface. Everything is ok so far, but when I add a second outgoing dispinterface VB doesn't see it. What do I need to do so my objects can support several different outgoing dispinterfaces?

        coclass MyCoClass
        {
        [default] interface IMyInterface;
        [default, source] dispinterface DIMyEvents1;
        [source] dispinterface DIMyEvents2; // VB doesn't see this!
        };

        L Offline
        L Offline
        Lost User
        wrote on last edited by
        #3

        You're right. It's exactly what I need. Thank you very much!

        L 1 Reply Last reply
        0
        • L Lost User

          You're right. It's exactly what I need. Thank you very much!

          L Offline
          L Offline
          Lost User
          wrote on last edited by
          #4

          Not quite! :-( The article explains how to do it with ATL and MFC clients, not with VB clients. ================== The original message was: You're right. It's exactly what I need. Thank you very much!

          1 Reply Last reply
          0
          Reply
          • Reply as topic
          Log in to reply
          • Oldest to Newest
          • Newest to Oldest
          • Most Votes


          • Login

          • Don't have an account? Register

          • Login or register to search.
          • First post
            Last post
          0
          • Categories
          • Recent
          • Tags
          • Popular
          • World
          • Users
          • Groups