See the question and my original answer on StackOverflow

What VB/VBA uses is the type library name, which by default is the type library's file name mangled in some way to comply with VB/VBA syntax.

With Midl, it can be defined with the helpstring attribute on the library, something like this:

[
    uuid(12345678-1234-1234-1234-123456789ABC), 
    helpstring("MyTest COM Component"), 
    version(1.0)
] 
library MyTest.Com 
{
    ...
};

With dscom, you can use dscom's DsComOverideLibraryName parameter, in .csproj, something like this:

<PropertyGroup>
    ...
    <DsComOverideLibraryName>MyTest COM Component</DsComOverideLibraryName>
    ...
</PropertyGroup>

And this is what you'll see from VB/VBA, once rebuilt:

Calling from VB/VBA