IDependency resolution from non-module assemblies

Topics: Writing modules
Mar 7, 2011 at 1:41 PM

We are developing a several modules and have decided to move some generic types to a separate assembly in order to be able to reuse it in several modules, but it seems that Orchard isn't resolving our types marked with IDependency interface that are not part of the module, but contained in the referenced library.

Any chance to deal with this? It looks like a very common thing :(

Mar 8, 2011 at 3:26 AM

You are correct Orchard doesn't support this by default. There is a workaround that could work thought: Make the "separate assembly" an Orchard module, and (optionally if you want to share this) have the other Orchard modules depend on it in Module.txt (so that when the "other" module is enabled, the "separate assembly" module will also be enabled).

Mar 8, 2011 at 10:13 AM

Thanks for your reply, I also see this as the only solution for now.