Only one .cs file exposes its classes into .tlb file.

[ssbae]

Hi~

I have two .cs files:

Class1.cs

namespace ClassLibrary1
{
    public class Class1
    {
        ...
    }
 
    public class Class3
    {
        ...
    }
 
}
 

Class2.cs

namespace ClassLibrary1
{
    public class Class3
    {
        ...
    }
}
 

Also I set [assembly: ComVisible(true)] and check the "Register for COM interop" on the project property.

The problem is that the .tlb file created by Visual Studio 2005(and tlbexp.exe) has only interfaces and coclasses have been defined in Class1.cs file.

i.e., Class1 and Class3 are shown in the .tlb file, but Class2 is not shown in the .tlb file.

What did I wrong?

[Shashi Sadasivan]

Hi~

I have two .cs files:

Class1.cs

namespace ClassLibrary1
{
    public class Class1
    {
        ...
    }
 
    public class Class3
    {
        ...
    }
 
}
 

Class2.cs

namespace ClassLibrary1
{
    public class Class3
    {
        ...
    }
}
 

Also I set [assembly: ComVisible(true)] and check the "Register for COM interop" on the project property.

The problem is that the .tlb file created by Visual Studio 2005(and tlbexp.exe) has only interfaces and coclasses have been defined in Class1.cs file.

i.e., Class1 and Class3 are shown in the .tlb file, but Class2 is not shown in the .tlb file.

What did I wrong?

because there is actually no class 2?
you have defined class 3 twice in both the files!!

if its a typo...i havent touched what you are trying to do, good luck

[ssbae]

because there is actually no class 2?
you have defined class 3 twice in both the files!!

if its a typo...i havent touched what you are trying to do, good luck

It's a typo.

The below is the corrected code.

Class2.cs

namespace ClassLibrary1
{
 
    class Class2 
    {
        ...
    }
}
 

Thank you anyway^^

[Frinavale]

It's a typo.

The below is the corrected code.

Class2.cs

namespace ClassLibrary1
{
 
    class Class2 
    {
        ...
    }
}
 

Thank you anyway^^

Was the typo the problem?
Or are you still having problems?

[ssbae]

Was the typo the problem?
Or are you still having problems?

I still have the problem.

Sorry for the confusion.

[Plater]

What kind of project is this? A library/dll project?

[ssbae]

What kind of project is this? A library/dll project?

It is a Class Library project.

Thanks.

[Plater]

So I made a class library.
I set COM visible to (true)

I have the following:
Class1.cs

namespace mytemplib
{
    public class Class1
    {
        public int class1INT = 0;
    }
    public class Class3
    {
        public int class3INT = 0;
    }
}
 

Class2.cs

namespace mytemplib
{
    public class Class2
    {
        public int class2INT = 0;
    }
}
 

And after a build, I add the DLL as a reference to another project.
I can then get at:

mytemplib.Class1;
mytemplib.Class2;
mytemplib.Class3;
 

just fine.


If you are trying to use them as COM objects, I think you need to create more GUIDs for them maybe? I'm not real clear on how to use them as COM (never really done it) so I don't know

[ssbae]

So I made a class library.
I set COM visible to (true)

I have the following:
Class1.cs

namespace mytemplib
{
    public class Class1
    {
        public int class1INT = 0;
    }
    public class Class3
    {
        public int class3INT = 0;
    }
}
 

Class2.cs

namespace mytemplib
{
    public class Class2
    {
        public int class2INT = 0;
    }
}
 

And after a build, I add the DLL as a reference to another project.
I can then get at:

mytemplib.Class1;
mytemplib.Class2;
mytemplib.Class3;
 

just fine.


If you are trying to use them as COM objects, I think you need to create more GUIDs for them maybe? I'm not real clear on how to use them as COM (never really done it) so I don't know

Thank you.

But the problem is going on.

[Plater]

Can you see all your classes in a managed code environment?

[balabaster]

Thank you.

But the problem is going on.

Okay, my demonstration possibly shows what you are missing:
[size=2][color=#0000ff][/color][/size][size=2][color=#0000ff][/color][/size]
[size=2][color=#0000ff]Class1.vb[/color][/size]

 Namespace Namespace1 
    <ComClass(ComClass1.ClassId, ComClass1.InterfaceId, ComClass1.EventsId)> _
    Public Class Class2
        Public Const ClassId As String = "<Put unique GUID in here>"
        Public Const InterfaceId As String = "<Put unique GUID in here>"
        Public Const EventsId As String = "<Put unique GUID in here>"
        Public Property2 As String
        Public Sub New()
            MyBase.New()
        End Sub
        Public Sub DoClassStuff()
            MsgBox("Class2 is doing stuff")
        End Sub
    End Class
    <ComClass(ComClass1.ClassId, ComClass1.InterfaceId, ComClass1.EventsId)> _
    Public Class Class3
        Public Const ClassId As String = "<Put unique GUID in here>"
        Public Const InterfaceId As String = "<Put unique GUID in here>"
        Public Const EventsId As String = "<Put unique GUID in here>"
        Public Property3 As String
        Public Sub New()
            MyBase.New()
        End Sub
        Public Sub DoClassStuff()
            MsgBox("Class3 is doing stuff")
        End Sub
    End Class
End Namespace
 

Class2.vb

 Namespace Namespace1 
    <ComClass(ComClass1.ClassId, ComClass1.InterfaceId, ComClass1.EventsId)> _
    Public Class Class1
        Public Const ClassId As String = "<Put unique GUID in here>"
        Public Const InterfaceId As String = "<Put unique GUID in here>"
        Public Const EventsId As String = "<Put unique GUID in here>"
        Public Property1 As String
        Public Sub New()
        End Sub
        Public Sub DoClassStuff()
            MsgBox("Class1 is doing stuff")
        End Sub
    End Class
End Namespace 
 

Further reading is also available here:
http://support.microsoft.com/kb/817248

It demonstrates all the steps you need to follow in order to make a component visible to VB6 (i.e. via a COM interface).

Obviously you'll need to translate to C# ;)