Connection point net interop no idispatch

Question

0.00/5 (No votes)

See more:

Because no library is created for COM Connection Points if I expose Connection Points directly to Net they appear in C# as being under my DLL's namespace. Is there a way to properly expose the Connection Point interfaces to Net without using IDispatch?

What I have tried:

wrapping the interfaces and brokering the connection.

Posted 25-Aug-18 15:15pm

extinction: life

Updated 30-Aug-18 11:53am

Add a Solution

2 solutions

Solution 1

Sounds like you have some problems in your build settings. Connection points are derived from iDispatch, so they are immanent and you need understand that technique better. Read the articel COM Connection Points to understand it better.

Tip: create a new project with the Visual Studio wizard and import your code into it. (or compare the settings with your project)

Posted 29-Aug-18 1:53am

KarstenK

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

extinction: life · Accepted Answer · 2018-08-30T11:54:00

the connection point interfaces are defined in OCidl.idl. all four interfaces derive directly from IUnknown interface and not IDispatch. the solution to my problem has nothing to do with project settings. i believe the core problem is i am not using atl. atl creates an automation server by default. when atl creates a connection point it creates either an automation interface, or a dual interface. there is nothing wrong with using a com 1.0 coclass. as for the namespace, it's just like having a class that derives multiple interfaces that derive from iunknown. when casting to iunknown, you should be casting through one of the derived interfaces.

at least that's my take on it.