How to publish an Orchard Core app - Orchard Core Nuggets
Let's imagine you've already created an Orchard Core app and now it's time to show it to the world. How do you publish it, or rather, how do you create its publish package?
When publishing an Orchard Core, or any .NET Core app (be it a desktop app for release or deploying a web app) you need to use the dotnet publish command (see its docs). For web apps running on Azure App Service our usual practice is to do a self-contained deployment, see the .NET Core publishing guidelines. A standard publish command for a 32b Windows App service is as following:
dotnet publish SolutionName.sln --configuration Release --runtime win10-x86 --output C:\path-to-package-folder --self-contained trueFor a 64b App Service the runtime would be win10-x64.
If you just want to do a quick debug publish then running dotnet publish in the folder of an Orchard-based web app’s solution without any parameters will create a published app in the YourWebApp\bin\Debug\netcoreapp3.1\publish folder.
For a PowerShell script that does a publish and then zips up the package see this script in our HipChat to Microsoft Teams Migration Utility.
Did you like this post? It's part of our Orchard Core Nuggets series where we answer common Orchard questions, be it about user-facing features or developer-level issues. Check out the other posts for more such bite-sized Orchard Core tips and let us know if you have another question!
James said
I don't have a url yet. I built a Orchard Core decoupled app for the local youth athletics group. I'm trying to publish it to GoDaddy, but running into issues. I can publish a generic net core 3 app. I was able create to set up and run locally. When I try publishing again I get a generic 500 error. GoDaddy hasn't been able to help. I am using sql light. I'm not sure if this would be the issue.
Anyway, I can't find much out there and was wondering if by chance you might know more.
Thanks
Zoltán Lehóczky said
A 500 error can be due to a variety of causes. However, you can most possibly find out the details of the error from the Orchard logs. You can find these under the App_Data/Logs folder.