warning MSB3391: does not contain any types that can be unregistered for COM Interop

Question

I\'ve made a simple C# DLL (that\'s part of a much larger project) using VS2005. I need to use the DLL in Excel via VBA code so I am using COM Interop on the assembly. I a

Answer 1

In the AssemblyInfo.cs file, make sure you have the following:

// Setting ComVisible to false makes the types in this assembly not visible 
// to COM components.  If you need to access a type in this assembly from 
// COM, set the ComVisible attribute to true on that type.
[assembly: ComVisible(true)]

UPDATE:

Read: How can I make use of .NET objects from within Excel VBA?

Which links to: http://richnewman.wordpress.com/2007/04/15/a-beginner%E2%80%99s-guide-to-calling-a-net-library-from-excel/

Answer 2

1. You need to have ctor without any params.
2. You should have GuidAttribute and ProgIdAttribute around the classes.
3. Its better to mark the assembly as ComVisible(false) and mark explicitly the classes that need export.
4. Use interfaces for your classes.

5. Make sure the you have GuidAttribute in the assembly level.

   [Guid("<PUT-GUID-HERE-1>")]
   [ComVisible(true)]
   interface IFoo
   {
       void DoFoo();
   }
   
   [Guid("<PUT-GUID-HERE-2>")]
   [ComVisible(true)]
   [ProgId("ProgId.Foo")]
   class Foo : IFoo
   {
       public void DoFoo()
       {
       }
   }
   

Answer 3

I saw a similar problem. I got an error like:

warning MSB3391: does not contain any types that can be unregistered for COM Interop.

I followed all the rules (ComVisible, etc.) but nothing worked.

Solution: I had to put something in the default constructor so that it would not be optimized away. The moment I had something there, the registration finished with no message and the component was visible in the registry.

Interesting note: a friend of mine managed to register the original DLL with the empty default constructor on his machine (64-bit Windows-7, VS2008-Professional, like mine). However, his REGASM.EXE was:

C:\Windows\Microsoft.NET\Framework64\v2.0.50727\regasm.exe

while mine was:

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe

So it could be some difference between versions of the .NET framework - maybe the later version is optimizing too much and the REGASM does not account for that.