.net assembly as COM

[alcabo]

Hello,

I have a .net assembly (.dll) exported and registered as COM.

I've invoked it from a script in Windows Scripting Host (WSH) written in
VBScript and it ran fine.

I'd like to invoke this component from macros of MsOffice2003 and I'm using
the Visual Basic Macro Editor to do that, but I get an error. This error
says: "File or assembly name XXXX, or one its dependencies, was not found",
and it has the code -2147024894.

I don't understand the source of that error because the same script works
fine in WSH (so the component is registered).

Any idea about this problem?

some limitation in Visual Basic of Office2003 to invoke a .NET assembly
registered as COM?

Thank you in advance

[Phil Wilson]

If you configure the fusion log viewer it should give you a clue about where
it's looking and what file it's looking for.

http://msdn.microsoft.com/library/de...uslogvwexe.asp
--
Phil Wilson [MVP Windows Installer]
----
"alcabo" <al****@discussions.microsoft.com> wrote in message
news:A2**********************************@microsof t.com...

Hello,

I have a .net assembly (.dll) exported and registered as COM.

I've invoked it from a script in Windows Scripting Host (WSH) written in
VBScript and it ran fine.

I'd like to invoke this component from macros of MsOffice2003 and I'm
using
the Visual Basic Macro Editor to do that, but I get an error. This error
says: "File or assembly name XXXX, or one its dependencies, was not
found",
and it has the code -2147024894.

I don't understand the source of that error because the same script works
fine in WSH (so the component is registered).

Any idea about this problem?

some limitation in Visual Basic of Office2003 to invoke a .NET assembly
registered as COM?

Thank you in advance