Hi. I have created an assembly and I believe i have done all the right things
to expose this assembly as a COM object. However, when trying to call a
method from Excel VBA I am getting "File or assembly name MyAssembly, or one
of its dependencies, was not found".

It's registered, strong named, GAC'ed, etc. Is there any way to trace the
call to see where it's failing?

Note that even though I see the assembly in the GAC, the "Available
References" dialog in Excel VBA shows the location of the dll as being the
original creation path (i.e. the output path of my project). No idea if this
has anything to do with it.

Thanks

Kevin

Kevin,

You can try using Fuslogvw.exe to see binding failures.


Mattias

fantastic, first i've heard of this tool. thanks mattias.

there are three entries in the fusion log, but the first entry appears to
show that fusion.dll is being loaded from the .NET 1.1 directory, but the
assembly was built using 2.0. Interesting...


*** Assembly Binder Log Entry  (19/05/2006 @ 09:09:23) ***

The operation failed.
Bind result: hr = 0x80131107. No description available.

Assembly manager loaded from: 
C:\WINNT\Microsoft.NET\Framework\v1.1.4322\fusion.dll
Running under executable  C:\Program
Files\Microsoft\Office_02\Office10\EXCEL.EXE
--- A detailed error log follows.

=== Pre-bind state information ===
LOG: Where-ref bind. Location =
C:/WINNT/assembly/GAC_MSIL/KevTestCOM/1.0.0.0__0a7eaebdc112262d/KevTestCOM.dll
LOG: Appbase = C:\Program Files\Microsoft\Office_02\Office10\
LOG: Initial PrivatePath = NULL
LOG: Dynamic Base = NULL
LOG: Cache Base = NULL
LOG: AppName = NULL
Calling assembly : (Unknown).
===

LOG: Processing DEVPATH.
LOG: Policy not being applied to reference at this time (private, custom,
partial, or location-based assembly bind).
LOG: Attempting download of new URL
file:///C:/WINNT/assembly/GAC_MSIL/KevTestCOM/1.0.0.0__0a7eaebdc112262d/KevTestCOM.dll.
LOG: Assembly download was successful. Attempting setup of file:
C:\WINNT\assembly\GAC_MSIL\KevTestCOM\1.0.0.0__0a7eaebdc112262d\KevTestCOM.dll
LOG: Entering run-from-source setup phase.
ERR: Error extracting manifest import from file (hr = 0x80131107).
ERR: Failed to complete setup of assembly (hr = 0x80131107). Probing
terminated.

UDP socket with multiple ports
DataGridViewComboBoxes for numeric fields
specify clr version
System.Windows.Forms.ColumnHeader and IDisposable
Remoting: security and app.config