What I did in the past when it came to expose C# classes to COM
was to create another class that defined the 'interface' to the COM world
and internally it would delegate its calls to the real C# class.
That way you can keep your overloads and you don't need to sacrifice
your conventions
solely to
I've played around a bit, and the *only* way I've made this happen is
to not use method overloading, but change them all into a single
method like this:
public void Method(string S, [Optional]string T)
Is this really the only way to do it? It means I have to collapse all
public overloaded met
In my C# class library, I have these ComVisible method overloads:
public void Method(string S)
public void Method(string S, string T)
If I set the ClassInterfaceType to AutoDual, these appear in VB6
intellisense like this:
Method_1(string S)
Method_2(string S, string T)
However, I would
Why not simply build your VB6 control w/ binary compat? This is not a .NET
problem -- it's what folks had to do to make VB6 controls work with
ordinary COM clients.
-S
===
This list is hosted by DevelopMentor® http://www.develop.com
Some .NET courses you may be i
Hi all,
I have a .NET application that use a VB6 active x dll (A) to perform
some actions. Now the problem is that when I recompile my VB6 dll I have
to recompile my .NET application. Is there a way to make our .NET so
that is will use the dll event when I recompile the dll?
I can think of one so
