Exposing COM functions?

[TommyIndigo]

I created an ActiveX DLL in VB that will send Outlook meeting requests to selected recipients. In testing the code (with hard-coded values), this seems to work fine. Now, I have edited my function to accept parameters, using Property Get/Lets. I would eventually like to pass parameters from a Perl script (which will be another question in itself).

I compiled and registered my DLL, however using QuickView in Explorer I notice there are only 4 functions exposed:
DllCanUnloadNow
DllGetClassObject
DllRegisterServer
DllUnregisterServer

I was expecting to see the function I created in the DLL, not these. Since my Perl script could only interact with exposed functions, I'm wondering if I need to somehow change my DLL to work with an exposed function (perhaps DllGetClassObject?).

The problem could be my DLL code or my understanding of these exposed functions. I'm completely lost. If anyone has any detailed suggestions, it would be MOST appreciated! Thank you

 

[jmarler]

What you are seeing in QuickView is the exposed APIs of the DLL, not the COM interfaces. Remember that not all DLLs are COM DLLs . . . some DLLs sre just a librarys of exported functions. If you want to specifically see any COM interfaces, try using OLE View. If you need to created exported APIs, then you will need to write the DLL in C++ . . . unless someone out there can tell me how to write exported API functions (not COM functions) in VB. - Jeff Marler

http://www.JeffMarler.com

(please note, that the page is under construction)