Call .NET COM object from unmanaged code

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

MacDermott - 29 Jun 2003 01:36 GMT

I've developed a COM object using VB.NET, and was happily calling it from an
Access application.
Then I tried to run it on another machine.
The second machine has the .NET framework installed, but not VS.
(It also has Access installed, of course.)
I have transferred the Access mdb file and the .tlb file from the .NET
application, and I have registered the .tlb file.

The Access application runs fine, but once it gets to instantiating the COM
object, it says
"Active X cannot create object"

Is there something else I need to have on the second machine for this to
work?
(Slightly OT side question - .NET also creates a dll file, but I can't
register it. What's it for?)

TIA -
- Turtle

Reply to this Message

Wray Smallwood - 29 Jun 2003 21:17 GMT

If you can run it on the test system, what you have done is create a CCW dll
from the .NET dll. The CCW dll is the one you register, but it also needs
the .NET dll which is the meat of the code.

Refer to: Microsoft .NET/COM Migration and Interoperability in the MSDN, and
any number of other articles it refers like: Exposing .NET Framework
Components to COM

You're working with the right ammunition, you just haven't figured out how
to get the safety off.

Wray

> I've developed a COM object using VB.NET, and was happily calling it from an
> Access application.
[quoted text clipped - 15 lines]
> TIA -
> - Turtle

Reply to this Message

Rate this thread:

Call .NET COM object from unmanaged code

Free Magazines