Exposing .Net Methods To VBA (COM)

I am currently in the process of extending my Excel VBA project using VB.Net and Visual Studio. I’ve created a working DLL, made it COM visible and registered, and referenced it from my Excel file.
      In my DLL, I have created a few classes (each with its own interface and explicit GUID to prevent errors caused by adding/removing methods/properties). I have successfully used these classes in VBA in this way:

Dim abc As New MyClass
abc.MyMethod

Open in new window


      The problem is that I have a few subs that I am trying to use that aren’t part of any class. These are in a module call “Misc”, as shown below:

Public Module Misc
	Public Sub MySub()

	End Sub
End Module

Open in new window


      I want to be able to call these from VBA, either by just saying:
Call MySub

Open in new window

Or
Call MyNamespace.MySub

Open in new window

     But when I try to call the sub, it can’t find it and I get “sub or function not defined”.
The only way I’ve been able to access the sub is to write a class and interface that simply calls that sub, but that seems like a lot of work just to call one sub, plus I also have to create a new instance of the class in VBA before I can call the sub, adding an extra line of code.
      Is there any way around this?
BROOKLYN1950Asked:
Who is Participating?
 
BROOKLYN1950Connect With a Mentor Author Commented:
I pretty much forgot about this question until I stumbled on it today. I have figured out my own solution and though its far from optimal it was the only thing I found that worked the way I needed it to.

I created a standard class with an explicit GUID and an explicit interface with en explicit GUID. This class has members named after the the ones in my module (static class). The members in the normal class call the members in the module.

The non-static class is exposed to COM the same was as my other non-static classes and I can call the members of my module through this class. At the same time, my VB.Net code can call the members straight from the module without need to create an instance of a class to use.

So in short, COM sees a non-static class, and .Net sees both a static call and a non-static class which has calls to the static class.

The downside to this is that I have to declare each of my members three times, which can get annoying, but at least it works!
0
 
CodeCruiserCommented:
Does following work?

Call Misc.MySub
0
 
Easwaran ParamasivamCommented:
There is an option. Change the module to NonInheritable (static) class and method as Shared (static) method. So that it could be called as Module.Method without more code changes.

http://stackoverflow.com/questions/436605/vb-net-how-to-reference-vb-net-module


HTH.
0
Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

 
BROOKLYN1950Author Commented:
I tried both your suggestions. I can't believe I didn't think of CodeCruiser's suggestion, but just as well I guess, 'cause unfortunately it doesn't work. As for EaswaranP's suggestion, I changed:

Public Module Misc

      Public Sub MySub

      ...

Open in new window

to

Public NotInheritable Class Misc

      Public Shared Sub MySub

      ...

Open in new window


      Unfortunately this didn't work either. I could not call the sub directly, no mater how explicitly I wrote it or how I used the "Call" statement. I could get the module (or class as it now is) to show up by saying:
Dim abc as MyNamespace.Misc

Open in new window

But when I tried:
Dim abc as MyNamespace.Misc
abc.MySub

Open in new window

I got an "object reference not set to instance of an object" error.

So no solution yet, but hopefully we're getting close.
0
 
Easwaran ParamasivamCommented:
You no need to declare using Dim. Just call the method as MyNamespace.Misc whenever you required. Thats it.
0
 
BROOKLYN1950Author Commented:
I tried that, as I said in my last reply,
I could not call the sub directly, no mater how explicitly I wrote it or how I used the "Call" statement.

I tried all of the below:
MySub
Misc.MySub
MyNamespace.Misc.MySub

Open in new window

And I also tried each of those prefixed with the "Call" statement (though I don't  think that would make a difference).
0
 
BROOKLYN1950Author Commented:
I figured out my own solution as explained in the answer
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.