We are using visual studio (2012) to develop our Orchard modules. We have around 6 modules, supported by about 8 class library projects, all within the same solution (along with a copy of the orchard 1.5 source). This works fine when running the project
from visual studio, or deploying direct from VS, but we have several solution management issues to overcome when packaging our modules and deploying them to fresh installations
Having reviewed several other posts in stack overflow etc could I first confirm my understanding of how Orchard works with regards to packaging and references.
"The command line orchard tool will package a module including all file based references, but will ignore visual studio "project references" when identifying which dlls to package in the module"
If this is true, does this not create an extra complexity when working with visual studio? I've had to add post build commands to my class libraries to copy the binaries to a lib location, and altered what were project references to instead by file based
references to the lib location.
Am I missing a trick here? Presumably it would be possible to amend the module packager to understand project based references for dlls. Would it be worth raising a feature request for this, or is there a simpler way to achieve this with VS?