C++调用C#类时CreateInstance实例化失败问题求助

Let's break down the most common reasons your CreateInstance call might be failing, along with step-by-step fixes to get your interop working:

1. COM Registration Issues (Most Likely Culprit) #

C# COM components don't register themselves automatically unless you explicitly tell them to. If your component isn't properly registered, Windows can't find it when your C++ code asks for it.

• Manual Registration: Use the .NET Framework's regasm.exe tool to register your assembly. Make sure you use the version matching your project's bitness (x86 vs x64):

  # For 32-bit components (use x86 Developer Command Prompt)
  regasm.exe YourCSharpAssembly.dll /codebase /tlb
  
  # For 64-bit components (use x64 Developer Command Prompt)
  C:\Windows\Microsoft.NET\Framework64\v4.0.30319\regasm.exe YourCSharpAssembly.dll /codebase /tlb
  

  • The /codebase flag tells Windows where to find your DLL (critical if it's not in the GAC).
  • The /tlb flag generates the type library (.tlb) you're importing in C++.

• Auto-Registration in Development: In your C# project properties, go to Build and check "Register for COM Interop". This will auto-register the component every time you compile, which is great for testing.

2. Bitness Mismatch Between C++ and C# #

This is another super common issue. If your C++ project is set to build for x86, your C# component must be registered as 32-bit (and vice versa for x64). Mismatched bitness will almost always cause REGDB_E_CLASSNOTREG errors.

• To verify:
  1. Open the Registry Editor and navigate to HKEY_CLASSES_ROOT\CLSID\{2913E43B-A184-4353-8F10-F233B260699F}\InprocServer32.
  2. Check the default value: it should point to mscoree.dll in either Framework (32-bit) or Framework64 (64-bit) folder, matching your C++ project's platform.

3. Validate CLSID and Namespace Spelling #

Double-check that the CLSID in your C++ code exactly matches the Guid attribute on your C# ComClass1 class. Even a single character typo will break things.

• Your C++ code has:

  class __declspec(uuid("2913E43B-A184-4353-8F10-F233B260699F")) ComClass1;
  

  Which matches the C# class's Guid: [Guid("2913E43B-A184-4353-8F10-F233B260699F")] – that looks correct, but it's worth confirming again.

• Also ensure the namespace in your C++ code (ESC_TEST::ComClass1InterfacePtr) matches the C# namespace (namespace ESC_TEST).

4. Get Detailed Error Information #

Instead of just knowing CreateInstance failed, get the actual HRESULT error code and message – this will pinpoint the problem instantly. Modify your C++ code to add error handling:

if (FAILED(hRes))
{
    _com_error err(hRes);
    LPCTSTR errorMessage = err.ErrorMessage();
    // Either print this message or inspect it in the debugger
    MessageBox(NULL, errorMessage, _T("COM Initialization Error"), MB_OK | MB_ICONERROR);
}

Common error codes to watch for:

• REGDB_E_CLASSNOTREG: Class not registered (fix with proper registration/bitness match)
• E_NOINTERFACE: Requested interface not found (check interface Guid or COM visibility)

5. Ensure C# Component is Properly Configured for COM #

Make sure your C# code has all the necessary attributes to expose itself as a COM component:

using System;
using System.Runtime.InteropServices;

namespace ESC_TEST
{
    // Explicitly mark interface as COM-visible
    [Guid("DCA71C5B-FC20-4A34-BF92-E59CBE4AB1BB")]
    [ComVisible(true)]
    public interface ComClass1Interface
    {
        [DispId(1)]
        void test();
    }

    [Guid("241EB2C8-578A-4D14-B059-CB00AFA9E1ED"), 
     InterfaceType(ComInterfaceType.InterfaceIsIDispatch)]
    [ComVisible(true)]
    public interface ComClass1Events { }

    // Mark class as COM-visible, use no auto-generated interface
    [Guid("2913E43B-A184-4353-8F10-F233B260699F")]
    [ClassInterface(ClassInterfaceType.None)]
    [ComSourceInterfaces(typeof(ComClass1Events))]
    [ComVisible(true)]
    public class ComClass1 : ComClass1Interface
    {
        public void test()
        {
            System.Diagnostics.Debug.WriteLine("AVIRAM !!!!!!!!!!!!!");
        }
    }
}

Key points here:

• Add [ComVisible(true)] to both the interface and class (your original code didn't have this explicitly, and while it might work implicitly, it's safer to declare it).
• Use .NET Framework as your target framework (not .NET Core/.NET 5+ – those require additional setup for COM interop).

6. Verify STA vs MTA Compatibility #

Your C++ code calls CoInitialize(NULL), which initializes the thread as a Single-Threaded Apartment (STA). C# COM components are STA-compatible by default, but if you've modified the threading model, it could cause issues.

• Ensure your C# class doesn't have a [ComVisible(false)] threading attribute, and that you're not trying to use it in a Multi-Threaded Apartment (MTA) context without proper setup.

Start with checking registration and bitness mismatch first – those are the most frequent causes of this issue. Once you get the detailed error message, you'll have a clear path to fix it.

内容的提问来源于stack exchange，提问作者Omer Amar