The Orchard.Web project has project references to the modules. This enables automatic copying of the output assemblies into the bin folder of the Orchard.Web project.
This should be project dependencies instead of project references.
In the Orchard solution, the Orchard.Web project has project dependencies on the modules. This enables automatic copying of the output assemblies into the bin folder of the Orchard.Web project.
This was the key to fixing my build and deploy issue. I wasn't aware that build dependencies would affect the publishing of binaries.
The documentation at http://docs.orchardproject.net/en/latest/Documentation/Source-code-organization/ states the following.
This should be project dependencies instead of project references.
This was the key to fixing my build and deploy issue. I wasn't aware that build dependencies would affect the publishing of binaries.