I have a custom module I've written on my dev box and I'm trying to package it for deployment to our QA/Production servers. It has some references to some 3rd party assemblies. Some of the referenced assemblies are referenced directly from the
file system, and some are nuget package references. When I use the packaging feature from the Orchard command-line (package create MyCompany.MyPackage c:\temp), I get a nuget package that contains all my directly referenced assemblies, but none of my
nuget referenced assemblies. Needless to say, when I deploy this to another server, the module crashes the site because it's missing references.
How do I force the packaging tool to include my nuget referenced assemblies? Is this a bug, or am I doing something wrong? I can work around this by making all my references directly to assemblies on disk rather than using nuget, but if
I can keep using nuget, I'd like to.