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

"alcabo" <alcabo (AT) discussions (DOT) microsoft.com> wrote

Make sure the assembly is in the GAC or in the same folder as Office.

I am guessing you put the assembly in %systemroot%\system32 so it would work
with WSH?

Peter

--
Peter Torr - http://blogs.msdn.com/ptorr
HD DVD Program Manager

Hello Peter,

The assembly is in the GAC.

At the moment, I don't know what's wrong. If I find out the problem, I'll
post the solution.

Alex
--

"Peter Torr (MS)" wrote:

"alcabo" <alcabo (AT) discussions (DOT) microsoft.com> wrote


Are you using CreateObject or are you adding a reference under Project ->
References?

Peter

--
Peter Torr - http://blogs.msdn.com/ptorr
HD DVD Program Manager

I'm using CreateObject as I did with the VBScript in WSH.


"Peter Torr (MS)" wrote: