.NET assembly only PARTIALLY exposed to COM

  • Thread starter Thread starter Andrew J. Marshall
  • Start date Start date
A

Andrew J. Marshall

I built my assembly with the "Register for COM Interop" box checked.

I could reference my assembly and see the classes, but IntelliSense and the
Object Browser could not see the methods nor properties.

I used TlbExp and RegAsm with the same result.

How can I get IntelliSense and Object Browser to see the details of my
classes?

Thanks,
Andrew J. Marshall
MCP (Visual Basic)
Fairfax, VA
 
Sorry for replying to my own post, but ...

This article http://www.u2u.net/ArticlePage.aspx?ART=msdncominterop by
Patrick Tisseghem is awesome and it gave me my answer ...

You need to (in VB.NET)
* import System.Runtime.InteropServices
* and prefix the class declaration with
"<ClassInterface(ClassInterfaceType.AutoDual)>"
for example, <ClassInterface(ClassInterfaceType.AutoDual)> Public Class
Foo

Rebuild and, VOILA, IntelliSense and Object Browser are happy.

Andrew J. Marshall
MCP (Visual Basic)
Fairfax, VA
 
You must log in or register to reply here.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Registration the TLB of .NET-COM-Assemblies (Interop) 1
.net assembly as COM 1
Deployment of assembly which has Com Interoperability. 1
.NET RTD/COM Problems on one user's machine 0
Expose a .NET interface to COM as an interface 3
Is that possible to call .net 2.0 com component fro .net 1.1application? 2
Is that possible to call .net 2.0 com component fro .net 1.1application? 1
Problems registering assembly for COM 3

Back
Top