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
CODE PROJECT For Those Who Code
  • Home
  • Articles
  • FAQ
Community
  1. Home
  2. General Programming
  3. COM
  4. Problem facing with connection points

Problem facing with connection points

Scheduled Pinned Locked Moved COM
comsysadminhelp
3 Posts 2 Posters 0 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.
  • R Offline
    R Offline
    Raj Prathap
    wrote on last edited by
    #1

    Hi, I'm using one COM component(exe), which implements the connection points also. I have a client which implements Sink interface also. The event the server fires is a method with a single argument BSTR. When the server fires the event, client gets the notification, but the BSTR value is invalid(empty string). The problem is also seen with ULONG parameter also. Please suggest a solution, and please suggest is it a good idea to have parameters in the event notifications. Also if two clients are connected to the server, only the client which caused the event to fire is getting the notification. Thanks and regards, Raja Pratap.

    H 1 Reply Last reply
    0
    • R Raj Prathap

      Hi, I'm using one COM component(exe), which implements the connection points also. I have a client which implements Sink interface also. The event the server fires is a method with a single argument BSTR. When the server fires the event, client gets the notification, but the BSTR value is invalid(empty string). The problem is also seen with ULONG parameter also. Please suggest a solution, and please suggest is it a good idea to have parameters in the event notifications. Also if two clients are connected to the server, only the client which caused the event to fire is getting the notification. Thanks and regards, Raja Pratap.

      H Offline
      H Offline
      HakunaMatada
      wrote on last edited by
      #2

      Could you post a bit of your code so we can see where the problem is?

      --- :beer: Hakuna-Matata :beer: It means no worries for the rest of your days... It's our problem free, Philosophy :jig: "I think my response was 'What idiot dreamed this up?'" -- Mary Ann Davidson, Oracle's chief security officer, in typical blunt manner, remembering her reaction to the company's scheme to brand its databases as "unbreakable."

      R 1 Reply Last reply
      0
      • H HakunaMatada

        Could you post a bit of your code so we can see where the problem is?

        --- :beer: Hakuna-Matata :beer: It means no worries for the rest of your days... It's our problem free, Philosophy :jig: "I think my response was 'What idiot dreamed this up?'" -- Mary Ann Davidson, Oracle's chief security officer, in typical blunt manner, remembering her reaction to the company's scheme to brand its databases as "unbreakable."

        R Offline
        R Offline
        Raj Prathap
        wrote on last edited by
        #3

        The problem got soleved. We have to make the server free threaded and make the class implementing the interface singleton and we need to in _tWinMain.. make sure that CoInitializeEx gets called. Just trial and error caused a break through. Thanks and regards, Raja Pratap

        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