Create/use Interop but still have to register dll?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Mike Eaton - 18 Oct 2005 23:15 GMT

Hi there,

I'm working on a simple VB.NET app in Visual Studio 2003 that uses classes
in the msxml4.dll. I added a reference in my project to the msxml4.dll and
VS created the Interop.MSXML2.dll. However, when I attempt to execute the
program, I get an error stating that the COM object with CLSID (that
corresponds to msxml) is not registered.

If I regsvr32 msxml4.dll and rerun it works great.

I thought the idea of generating the Interop was so that the COM object
didn't have to be registered on the executing machine. Is this not the case?
or do I perhaps have something configured improperly in the way the interop
was built?

Does anyone have a reference on the subject that might give me some
guidance? I've looked on MSDN and am still not getting it.

Thanks so much.
Mike

Reply to this Message

Jason Newell - 19 Oct 2005 02:00 GMT

Mike,

Referenced COM dll's must be registered via regsvr32 for Interop to work.

The idea of COM Interop is to allow a .NET client to interact with a COM
client and vice versa. The COM requirements have not changed.

Adam Nathan is the man on COM Interop.
http://blogs.msdn.com/adam_nathan/

And his book:
http://www.amazon.com/exec/obidos/ASIN/067232170X

MSDN Article I found:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/comi
nterop.asp

Good luck!

Jason Newell

> Hi there,
>
[quoted text clipped - 16 lines]
> Thanks so much.
> Mike

Reply to this Message

Mike Eaton - 19 Oct 2005 16:15 GMT

Hi Jason,

Okay, now I've got the picture :-) Thanks so much for helping to clear
things up for me. The resources you suggested were very helpful.

Mike

> Mike,
>
[quoted text clipped - 15 lines]
>
> Jason Newell

Reply to this Message

Create/use Interop but still have to register dll?

Free Magazines