Resulting DLL Cannot be added as reference in VBA

[TheAxeManGa]

Hello! I've done my utmost to create a com-exposed DLL that can be added as a valid reference to a VBA project in Excel and/or Access.

This very vaguely covers creation of a manual IDL or C++ header and I have no clear direction on how to create these files so I can finally instantiate a new class in VBA derived from the classes in my DLL.

This used to be absolutely TRIVIAL in .NET Framework with Visual Studio (2 clicks!) .NET 6 seems to be a nightmare.

Additional documentation is needed to clarify the creation of a TLB derived from a .NET 6 DLL.

Thanks!

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: e0842844-005f-5004-022d-fce7a82daff8
• Version Independent ID: 88ddeba8-3b31-95f4-26b2-4a12a7313b47
• Content: Exposing .NET Core components to COM
• Content Source: docs/core/native-interop/expose-components-to-com.md
• Product: dotnet-fundamentals
• GitHub Login: @jkoritzinsky
• Microsoft Alias: jekoritz

---

Associated WorkItem - 599910

[adegeo]

Doing some searching on the subject, it seems Microsoft still doesn't provide CLI tools related to COM that were provided for .NET Framework. I did come across this: https://github.com/dspace-group/dscom which seems to replicate those tools. I think a note at the end of the article should be created that links to these tools.