File or assembly, or dependencies, not found

Author Topic
Darren Doody
Member

Joined: 21 Jan 2008
Country: Australia
Posts: 1

Posted: 21 Jan 2008 11:24:19

Hi all,

I have a vb6 dll that is attempting to call a vb.net (2005) dll via COM interop.

The moment the vb6 component attempts to instantiate an object from the .NET dll, it errors with:

File or assembly name XXX, or one of its dependencies, was not found.

As near as I can tell, all of the non-framework components the .net dll uses live in the same directory as the troubled component. This is possibly not the case though, given the message.

Also, as near as I can tell the vb.net component is correctly set up for COM interop (it was upgraded from an old vb6 component). I have no issues compiling the vb6 component against the COM reference exposed by the .net dll and those references are stable across multiple builds.

It may or may not be relevent, but the vb6 dll is an automation add-in to MS Excel. The .net component does not reference Excel or Office.

I am fluent in vb6 but new to .net. Any help to track down the source of this error would be much appreciated.

Hi all,

I have a vb6 dll that is attempting to call a vb.net (2005) dll via COM interop.

The moment the vb6 component attempts to instantiate an object from the .NET dll, it errors with:

File or assembly name XXX, or one of its dependencies, was not found.

As near as I can tell, all of the non-framework components the .net dll uses live in the same directory as the troubled component. This is possibly not the case though, given the message.

Also, as near as I can tell the vb.net component is correctly set up for COM interop (it was upgraded from an old vb6 component). I have no issues compiling the vb6 component against the COM reference exposed by the .net dll and those references are stable across multiple builds.

It may or may not be relevent, but the vb6 dll is an automation add-in to MS Excel. The .net component does not reference Excel or Office.

I am fluent in vb6 but new to .net. Any help to track down the source of this error would be much appreciated.
Follow us on twitter Subscribe to our RSS feed
Activate your free membership today | Login | Currency