Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
When publishing a orchard web site from visual studio 2010/2012 it works to publish in release mode for Orchard 1.5.1 then you get a portable ~50MB site.
But for Orchard 1.6 it does not copy the neccesary files/folders unless you choose Debug mode which is to big to consider uploading sometimes ~800MB , why is this ?
We have reverted to 1.5.1 for the time being…
You need to go to the Package/Publish Settings for the Orchard.Web project, find option “Items to deploy”, and change it’s value to “All files in this project folder”. Make sure that the current configuration context is set to Release.
Currently it’s value is set by default to “Only files needed to run this application”. As a result, some important sub-directories of the Orchard.Web, like Themes and Modules, are not get published, because they are not included into the project file.
NOTE: In order to decrease generated output folder size you need check option “Exclude generated debug symbols” below the “Items to deploy”.
BTW, As far as I remember, this issue is relevant for the previous versions too.
As far as I understand, it’s more correct to use
build.cmdfile for building deployment package instead of using Publish command directly from VS. This way you can also utilize new Precompiled target feature, intoduced in Orchard 1.6. It provides ability to precompile all modules and themes, and publish them as DLLs.