Using .NET Class library in VB 6.0

here is a very good codeproject article on this issue.
http://www.codeproject.com/KB/COM/cominterop.aspx#PART2

The onlt thing the article(s) did that i didn't do is adding [ClassInterface(ClassInterfaceType.AutoDual)] before my class in .NET.  I added that but it didn't make any difference..

Hi axnst2,

If you do the following things - define interface, ijmplement this interface in your class, and mark it with
[ClassInterface(ClassInterfaceType.AutoDual)] attribute (in addition to what you have kusted abve) - it should work. I have concern about error message you receive - maybve there is a type in your class that .net interop cannot convert to COM. Can you showe your interface/class definition? Do you have any user defined types in methods exposed to the COM?  

.NET code:

using System;
using System.Collections.Generic;
using System.Text;
using System.Runtime.InteropServices;
 
namespace NET_to_COM
{
    [ClassInterface(ClassInterfaceType.AutoDual)]
    public class CFootPedalMonitor
    {
        public CFootPedalMonitor()
        { }
    }
}
                                              

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:

VB Code

Private Sub Form_Load()
 
Dim footPedalMonitor As NET_to_COM.CFootPedalMonitor
 
End Sub
                                              

1:
2:
3:
4:
5:

Your CFootPedalMonitor() method does not return any types, it should either return some type or void

not when it is a constructor.

Oops. Overlooked it. Sorry. I just assumed there should be at least one methond to call. Thanks jamesrh.

So then I really don't see any issue here. Isn't it the fact that there are no methonds at all? I have never tried it. Have you tried to add methods?

Exactly...I am not sure what I am doing wrong...

I have put the DLL and the .tlb in the same folder as the VB project is...

What's starnge, as I mentioned before, is that VB recognizes the namespace because if I type "NET_to_cOM.CFootPedalMonitor" it changes it to "NET_to_COM.CFootPedalMonitor" but then when I run it it gives me the error...

As you are making these changes on the .NET side are you droping and readding the reference in VB

jamesrh: I am not sure what you mean?

sqomzin: I tried addeing a test function but it didn't amke a difference

OH...I know what you mean now...yes I am

I tried that...that doesn't make a difference either..

That wasn't it either... I changed my code to what's below and it didn't make a difference...

using System;
using System.Collections.Generic;
using System.Text;
using System.Runtime.InteropServices;
 
    [ClassInterface(ClassInterfaceType.AutoDual)]
    public class CFootPedalMonitor
    {
        public CFootPedalMonitor()
        { }
 
        public void Test() { }
    }
                                              

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:

I am on the C# side, let me check how the exact VB client code looks like with the guy who was actually doing the VB part.

When I use the below VB code I get the following error:

"Run-time error '429':

ActiveX component can't create object"

Private Sub Form_Load()
 
   Dim obj As Object
   Set obj = CreateObject("NET_to_COM.CFootPedalMonitor")
 
End Sub
                                              

1:
2:
3:
4:
5:
6:

Is NET_to_COM the dll name?

so you are using late binding here... you may redefine the prog id in your C# code so you can use exctly the same prog id in your VB client. You need to add this attribute top the class:
[ProgId("NET_to_COM.CFootPedalMonitor")]

Yes...

Previously I wasn't but I just wanted to try something different...
I added the ProgID and it made no difference...

I am wondering if maybe I am not doing something right when it comes to the registration of the DLL

Here's the code I've been using to register the dll:

cd C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
Regasm "C:\Program Files\Microsoft Visual Studio\VB98\NET_to_COM.dll" /tlb:"C:\Program Files\Microsoft Visual Studio\VB98\NET_to_COM.tlb"

                                              

1:
2:

When I unregister it, I get the following message:

That warning is interesting?

so the early binding VB code should be like this:

Private oNetCom As NET_to_COM.CFootPedalMonitor

Set oNetCom = New NET_to_COM.CFootPedalMonitor

Yeah...that's what I had before...

try to register this way:

cd C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727

Regasm  /tlb:"C:\Program Files\Microsoft Visual Studio\VB98\NET_to_COM.tlb"  /code "C:\Program Files\Microsoft Visual Studio\VB98\NET_to_COM.dll"

OK!  We finally got it!  Here's what I had to do:

1.  I had to get rid of the namespace and have just the class in the DLL.
2.  I had to add the all the attributes we discussed above
3.  I registered the DLL using this:
     _____________________________________
     cd C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727
     Regasm "C:\Program Files\Microsoft Visual Studio\VB98\NET_to_COM.dll" /tlb:"C:\Program Files\Microsoft Visual Studio\VB98\NET_to_COM.tlb"
    ______________________________________

4.  And I had to place the DLL and tlb in the above VB98 folder in order to run it in debug mode

If I change any of the above 4 things, it does not work.....

Below I am including both the .NET and VB code for the next poor bastard...

Guys....thank you a million times!

//.NET CODE:
//___________________________________________________________________
using System;
using System.Collections.Generic;
using System.Text;
using System.Runtime.InteropServices;
 
    [ClassInterface(ClassInterfaceType.AutoDual)]
    [ProgId("NET_to_COM.CFootPedalMonitor")]
    [ComVisible(true)] 
    public class CFootPedalMonitor
    {
        public CFootPedalMonitor() { }
 
        public void Test() { }
    }
//___________________________________________________________________
 
//VB Code
//___________________________________________________________________
Private Sub Form_Load()
   Dim footPedalMonitor As NET_to_COM.CFootPedalMonitor
   Set footPedalMonitor = New NET_to_COM.CFootPedalMonitor
   Call footPedalMonitor.Test
End Sub
//___________________________________________________________________

                                              

1:
2:
3:
4:
5:
6:
7:
8:
9:
10:
11:
12:
13:
14:
15:
16:
17:
18:
19:
20:
21:
22:
23:
24:
25:
26: