Exposing vb.net procedures -- dotnet interop

Jonathan West
12/26/2003 8:04:54 PM

Hi John,

The VB.NET project must be saved as an ActiveX DLL. Then you can access the
DLL either by setting a reference in Tools References in the VBA editor, or
by using late binding, and creating an object variable with the reference
using the CreateObject command.

--
Regards
Jonathan West - Word MVP
http://www.multilinker.com
Please reply to the newsgroup

[quoted text, click to view]

Frank Oquendo
12/27/2003 12:19:44 PM

[quoted text, click to view]
http://msdn.microsoft.com/library/en-us/vbcn7/html/vaconCOMInteroperability.asp

I never did like the ComClass attribute. I prefer the absolute control
of ComVisible, ProgId, Guid and ClassInterfaceType in conjunction with
interfaces.

--
There are 10 kinds of people. Those who understand binary and those who
don't.

http://code.acadx.com
(Pull the pin to reply)

John
12/27/2003 3:32:11 PM

Hi

How do I save the vb.net app as activex dll? Is activex dll supported in
..net apps?

Thanks

Regards

[quoted text, click to view]

Armin Zingler
12/27/2003 6:47:49 PM

"John" <john@nospam.infovis.co.uk> schrieb
[quoted text, click to view]

See Herfried's link. See also the Framework documentation:
http://msdn.microsoft.com/library/en-us/cpguide/html/cpconexposingnetframeworkcomponentstocom.asp

See also the VB.NET documentation:
http://msdn.microsoft.com/library/en-us/vbcn7/html/vaconCOMInteroperability.asp

--
Armin

http://www.plig.net/nnq/nquote.html
http://www.netmeister.org/news/learn2quote.html

Got something to say? Click here to post a reply to this thread.

Don't see what you're looking for? Try a search.

View other messages about dotnet interop

dotnet interop : Exposing vb.net procedures