We have developed several (closed source) modules we want to share between different orchard solutions.
For Orchard to pick up a module, it needs to be placed in the Modules folder of a solution. So from a file-based perspective, we need to copy the entire module from one solution to another.
However, these modules are still in development so this approach is not very flexible.
There has to be a better way of doing this... 2 ideas came to mind:
- Setting up a private "module gallery". One solution pushes an updated version of the module to the gallery so the other solutions can upgrade. Has anyone done this?
- We are using TFS for source control. Maybe it's possible to create "virtual maps" that point to the same branch?
I'm sure most of you have modules that are reused in different solutions. How do you deal with this?