Register a dll that references multiple dlls

Question

Ok I have 2 questions and I'm in a pickle here and have been for a week.

Important - No application will build this or run it. It will be a single client side dll (that references several other dll's) that will be placed in specific folder and I will need to register this dll using regasm or something.

OverView:

So I have ac# COM ScannerController.dll written. ScannerController references five 3rd party dll's that will already be installed and registered in folders throughout c:\\Program Features\\etc.... (the locations will change depending on the version of the software that they are on, but the dll will be the same.)

This one dll (integration.ActiveX (it's an assembly)) has a method called InstalledPath. InstalledPath returns the actual location of the executing assembly. When I finished the dll I ran it through IExplorer and it was returning the correct "../program features/....".

Then, in order to set it up on another computer I unregistered it and then ran some regasms and registered the dll at "Scanner/bin/debug/integration.ActiveX" (which oleview says it can't find it's dependencies) So I unregistered it, built it in vs2012 and now when I run it from IExplorer, the InstalledPath is "../bin/debug/". I created a new projecte, built it which auto registered it, and ran it from iexplorer and the InstalledPath is "..Scanner-fake/bin/debug/". I've unregistered it a million times in cmd and no matter what I do, it is now always pointing at the debug folder of the registered ScannerController.

Question 1:

How in the world do i register my COM ScannerController.dll, using something like regasm, and also point it to the five 3rd party dlls that ScannerController references?

Question 2:

I tried fixing it to where Integration.dll wouldn't exists in the local path on my computer (since i'm building it) so I set the copy local to false. When I build it, view it in oleview, it says that its dependencies cannot be loaded or found. How can I set the project up so that, with the copy local = false, the references can find the other 3rd party dlls?

Sorry for the lengthy question but thank you so much for reading and attempting to help me out. I have searched high and low for this and I am just mentally exhausted now.

Answer 1

1) ScannerController.dll

COM registration using regasm ScannerController.dll

2) 3rd Party ActiveX dll

Assuming it's already registered: No action required. (Otherwise register with regsvr32 )

3) 3rd Party Managed Libraries (no com types/libsexposed)

Use one of the following 2 option to guarantie that your ScannerController Libraray can access these managed libraries:

• Copy them to the folder where your ScannerController.dll or maybe (I am not 100% sure, you have to test it) to the folder where the ScannerController.dll host - the exe / the process calling ScannerController.dll - resides
• Register these libs in the global assembly cache (the registry pendant for managed libraries) to make them globally available to other applications