.NET COM组件注册后提示‘对象无属性或方法’问题求助

It looks like you’ve covered a lot of the basic COM interop configuration steps, but there are still a few environment-specific and setup details that might be causing those "Failed to create object" or "Object has no properties or methods" errors. Let’s break down targeted fixes for your Windows Server 2008 R2 + VB6 scenario:

1. Match RegAsm Bitness to Your VB6 Application #

VB6 applications are 32-bit only, so you must use the 32-bit version of RegAsm to register your DLL (even on a 64-bit OS). Using the 64-bit RegAsm will create registry entries that 32-bit VB6 can’t access.

• Use this 32-bit RegAsm path:
  C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe
• Always register with the /codebase flag (since your DLL isn’t in the GAC):

  RegAsm.exe YourAssembly.dll /codebase /tlb:YourAssembly.tlb
  

• Run Command Prompt as Administrator to ensure registry write permissions.

2. Fix Interface & Class Attributes for VB6 Compatibility #

Your interface is missing a critical InterfaceType attribute that enables VB6 to call methods via IDispatch. Update your code like this:

using System;
using System.Runtime.InteropServices;

namespace project_name
{
    // Mark interface as IDispatch for VB6 compatibility
    [Guid("EAA4976A-45C3-4BC5-BC0B-E474F4C3C83F")]
    [ComVisible(true)]
    [InterfaceType(ComInterfaceType.InterfaceIsIDispatch)]
    public interface ComClass1Interface
    {
        [DispId(0)] // Sets this as the default method (optional but helpful for VB6)
        [ComVisible(true)]
        double calc();
    }

    // If you don't use events, you can mark this as ComVisible(false) to simplify
    [Guid("7BD20046-DF8C-44A6-8F6B-687FAA26FA71")]
    [InterfaceType(ComInterfaceType.InterfaceIsIDispatch)]
    [ComVisible(false)]
    public interface ComClass1Events
    {
    }

    // Add ProgId for easy VB6 object creation (e.g., CreateObject("project_name.ComClass1"))
    [Guid("0D53A3E8-E51A-49C7-944E-E72A2064F938")]
    [ClassInterface(ClassInterfaceType.None)] // Ensures only your explicit interface is exposed
    [ComSourceInterfaces(typeof(ComClass1Events))]
    [ProgId("project_name.ComClass1")]
    [ComVisible(true)]
    public class ComClass1 : ComClass1Interface
    {
        public double calc()
        {
            return 13;
        }
    }
}

3. Compile for x86 Architecture #

VB6 can’t load 64-bit .NET assemblies. Ensure your project targets x86:

1. Right-click your project in Visual Studio → Properties
2. Go to the Build tab
3. Set Platform target to x86
4. Rebuild your assembly before registering.

4. Verify Registry Entries #

After registration, check the 32-bit registry hive to confirm entries exist:

1. Open regedit.exe
2. Navigate to HKEY_CLASSES_ROOT\Wow6432Node\project_name.ComClass1
   • Ensure the CLSID subkey points to your class’s GUID
   • Check InprocServer32 has the correct path to mscoree.dll and your DLL’s CodeBase is set
3. Confirm your interface’s GUID exists under HKEY_CLASSES_ROOT\Wow6432Node\Interface\{YourInterfaceGUID}

5. Enable COM Event Logging for Deep Troubleshooting #

If the above steps don’t work, enable COM logging to get detailed error messages:

1. Open regedit.exe and navigate to HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run
2. Add a string value named COMLOG with the value:
   rundll32.exe comsvcs.dll,EventLogging
3. Restart the server
4. Attempt to create the COM object in your VB6 app
5. Check the Event Viewer → Applications and Services Logs → Microsoft → Windows → COM+ for specific failure details (e.g., missing dependencies, permission issues)

6. Check DLL Permissions & Dependencies #

• Place your DLL in a non-system directory (e.g., C:\Program Files (x86)\YourCOMApp) and grant Read & Execute permissions to the user running the VB6 app.
• Ensure all dependent DLLs (if any) are in the same directory or registered in the GAC.

内容的提问来源于stack exchange，提问作者Mahyar Mottaghi Zadeh