Skip to content

Orchard.Web project dependencies for modules #353

@cadull

Description

@cadull

The documentation at http://docs.orchardproject.net/en/latest/Documentation/Source-code-organization/ states the following.

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions