Reputation: 91
Over the last 2 days i twisted my head around deploying my WEB API.
App specification: WEB API .NET CORE 3.0 Preview 4
Firstly i tried to deploy on Azure using App Services. Seems like they don't support .net core 3.0 but i don't really understand this since you can wrap everything in your package, wasn't this done in order to be deploy-able everywhere ? When i'm trying to access the websitei get a HTTP Error 500.0 - ANCM In-Process Handler Load Failure which i didn't managed to fix.
--I tried to do the same with a clean project, still same issue--
Secondly i created a virtual machine (VM) and deploy on VM.
Here i get a internal server error and i cannot debug (any tips are welcome)
Third I deployed on local IIS, here i get the following error: "Cannot read configuration file due to insufficient permissions"
I added the permissions to IIS_IUSRS but after this i get a infinite loop
--The same i get with the clean project--
Am i doing something wrong , what could i do to deploy my Web Api Project.
Upvotes: 6
Views: 2292
Reputation: 5403
The documentation suggests that it is possible to deploy preview versions, although I haven't tried it. This blogger encountered the same problem you did, and resolved it using these instructions. He says:
This document covers two different ways to fix this issue – you can either install the preview site extensions for ASP.NET Core 3, or you can simply change your deployment to be a self-contained application. In this case we’re going to go with deploying a self-contained application, since this reduces any external dependencies which seems sensible to me.
So it seems you are correct that building a self-contained package is one way of solving this, but you have to specifically ask for that when you publish.
Upvotes: 6