Re: Calling VB.net from C++

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

joshturner1967 <joshturner1967@xxxxxxxxx> wrote:
On Oct 9, 9:36 am, "Igor Tandetnik" <itandet...@xxxxxxxx> wrote:
What you do is register your .NET assembly as a COM server. See

http://msdn.microsoft.com/en-us/library/zsfww439.aspx

I tried letting the compiler do it

Letting which compiler do what?

and by doing that it allowed me to
do com calls to it through a legacy system com call process - This
does nothing fancy other than make normal com calls based upon your
input

Are there "abnormal" COM calls, as opposed to normal ones? What else
besides "making normal COM calls" do you expect to be able to do?

I also tried Regasm.exe but that did not do anything either.

What did you expect it to do, and in what respects did it fail to meet
your expectations?

In fact
I first tried it on the location of the compiled dll and then put the
fully qualified path into the #import statement

You don't #import a .NET DLL. You use TlbExp tool to generate a type
library from said DLL, and #import that.
--
With best wishes,
Igor Tandetnik

With sufficient thrust, pigs fly just fine. However, this is not
necessarily a good idea. It is hard to be sure where they are going to
land, and it could be dangerous sitting under them as they fly
overhead. -- RFC 1925


.

Relevant Pages