I have a WPF application, which I build as a dll COM component and install using installshieldLE, however I have some issues with some dependent dlls, when running my COM client.

My WPF dll references two other C# dlls (A & B) which reside within the same VS2012 solution.

My WPF dll has the register for COM interop option checked and provides a COM interface for running the WPF GUI application.

I have a C COM client program, which tests the WPF application. The problem I am having is that I need to include some of dll\_A's referenced dlls, (which is a third party graphics package) in the folder of the client program for the application to run successfully. I don't have to include dll\_A or dll\_B in the local client directory. 

Also, there are other (C) dlls referenced by the COM server dll and included in the installation that do not need to be present in the client directory, so this is difficult to understand.

I assume that this is not a WPF question but simply a question about com server installation in relation to other referenced assemblies.

I have output some debug messages in the primary dlls that confirm that the dlls A&B, along with the main COM dll are being run from the installation location. But I get exceptions further down the line when the third party dlls are missing from the local client folder.

Can someone help me troubleshoot this problem please. I can run the client program successfully from the installation location and am therefore certain that all required assemblies and dlls are present.

Thanks.