0

Consider the following scenario:

I have two assemblies:

  • Assembly named A.dll located in folder Fold_A
  • Assembly named B.dll located in folder Fold_B

A.dll depends on B.dll and A is COM visible when I'm performing command:

regasm A.dll /codebase

It fails, but when B was copied into fold_a - the command succeeded.

Is there some way to perform without copying assemblies on which depends assembly to be registered (by regasm)?

There is already question related to the issue: Multiple search paths for assemblies not in the GAC when using REGASM & COM

Peter Mortensen
  • 30,738
  • 21
  • 105
  • 131
lm.
  • 4,033
  • 4
  • 25
  • 37

1 Answers1

1

Well, yes, it is a problem when you register it but it will be a much larger problem when a client actually uses your COM server. A typical COM client will be unmanaged code, it isn't very practical to give it, say, a .config file to tell the CLR where to look for assembly B.

If you want this to work for any client without config then you ought to put B in the GAC. Which in general is the proper place for COM servers, DLL Hell is nothing to mess with when you use COM. Using the Assembly.AssemblyResolve event is probably not going to be practical but you could try by using a static class constructor to register the event handler. Hard coding the path to dependencies is questionable unless those folders are always related.

Hans Passant
  • 922,412
  • 146
  • 1,693
  • 2,536