I have this vb project that I compile separately to a .dll.

I referenced the .dll in this other ("client") project.

Here's one of the classes that I defined in the vb .dll project:

Imports Microsoft.Office.Interop
Public Class fwExcel
    Implements IDisposable

In the client project I cannot "using" it, because it's "IDsposable" is not recognised.

Under that fwExcel class I also defined :

   Public Class fwWorksheet

This class does have a constructor :

        Public Sub New(oXl As fwExcel)
            Me.oXlParent = oXl
            Me.oXl = oXl.oApp
        End Sub

Interestingly, for some reason, the client does not "see" this fwWorksheet Class.

On the other hand, it does recognize a fwSQL.sqlBulider that was defined similarly but does not have a constructor. I'm mentioning that because that's the only difference that I can think of.

Am I missing something when I reference the .dll. Is there something more I have not done when I "built" the vb.dll as a "second" project within another solution?

TIA and kind regards,

Marc