G
Guest
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
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