.NET Core Web App Development
I recently began working on an existing project that is an API written in .NET Core 2.1. After finishing the changes, I ran into a problem. I needed to deploy the app, but I do not have access to the IIS server. My .NET web development experience has always involved stopping the site in the IIS Manager app, copying the files, and starting the site back up. Without doing that, there would always be a file lock on at least one of the files.
Does .NET Core behave the same way? Yes it does. I did some reading online to see if there was a way around it. To my surprise there is. Create a file called app_offline.htm and place it in the application root. IIS server will serve that file instead of the web app, thus removing any file locks.
Problem: Can not deploy a .NET application to IIS without access to IIS on the server.
Solutions: Create a file called app_offline.htm and place it in the application root on the web server.