Performance when using a large number of dlls

See more:

performance

C#5.0

We are building a solution for a generic application that can have dlls removed/reinstated to support flexibility of the internal modules. It is required as a platform that a specific implementation can replace existing modules with ones it wants to run/test etc.

For example, a specific implementation can simply write it's own dll to replace the original ModuleA and it works fine since the fitted new ModuleA replacement implements IModuleA. In this way, a user of the application can fit in his modules without having to compile the generic application.

To allow this kind of methodology, any replaceable module is it's own project, thus complied to another dll.

My question: Is there any performance hindrance working like that with numerous dlls instead of a small number of dlls?