ATL COM events crash in "windows embedded compact 2013" vs2013-project

Question

0.00/5 (No votes)

See more:

Hello, we are developing software for a 'Smart Device' for WEC2013 using VS2013.

Basis is a C++ ATL COM Project (ATL Simple Object with Connection points) using the 'Smart Device' specific SDK, which results in a DLL.
That DLL is referend by a C# 'Device Application'-Project (.NET Compact 3.9). Everything compiles and builds fine. But connecting an ATL COM object event with the event handler of the C# client:

comObj.TestEvent += (_ISimpleComEvents_TestEventEventHandler) comObj_TestEvent;

crashes with the exception: "COM interface with IID '{00000000-0000-0000-0000-000000000000}' cannot be created due to the following error: No such interface supported."

Thanks for any suggestion.

What I have tried:

The same mimik is running fine, when build with VS2005 for Windows Embedded CE6.0 R3 for the same 'Smart Device'.

Posted 29-Jun-20 9:25am

Member 14875971

Updated 29-Jun-20 22:29pm

Add a Solution

Comments

Member 14875971 30-Jun-20 10:03am

Thanks Richard for your answer, I agree. But why does the connection point interface UUID appears to be zero? The connection point interface is defined with a 'reasonable' UUID in the IDL file. I used the vs2013 wizards as much as possible for setting up the project. And I did all steps simultaneously in another vs2013-session to set up the same project for (desktop) Windows 7, where everything, inclusive the event mechanism, is working fine.

1 solution

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)

Richard MacCutchan · Answer 1 · 2020-06-29T22:29:00

Solution 1

You cannot use a null GUID to refer to a COM interface. Check the actual value that it use to register itself.

Posted 29-Jun-20 22:29pm

Richard MacCutchan