Hi Roland,
If you are using SnapDevelop, it uses .Net Core. The Publish option in SnapDevelop can package all the runtime files you need depending on what option you choose. I've deployed a few web services written in SnapDevelop and I publish using the Docker option. It packages everything up into a Linux container (although you can choose Windows if you want) and I then deploy the container to a Linux server for production. The web services are then accessed via reverse proxy from Nginx webserver, although they could be accessed directly if we want.
I have tried the File System publishing in SnapDevelop. However, the official Appeon documentation does not explain the subsequent procedure so that the files generated in the publication can then be installed as an application in IIS. Could you please tell me what this procedure is and what are the IIS configuration items that you mention?
I have already “Googled” several pages on this subject and have followed the instructions there exposed. However, after installing, when browsing the application directly from IIS, I get error 500.19 (Internal server error) related to the inaccessibility of the web.config file; Do you know anything about it?
https://www.c-sharpcorner.com/article/deploy-asp-net-core-api-application-in-iis/
For that specific 500.19 error it says "The problem is, to run the .NET Core application in IIS we need to install “dot net core windows hosting bundle”. Just download and install it using the below link."