Making ASP.NET Core apps always running on IIS

[gustafsonk]

From my personal experience just recently with getting an ASP.NET Core 3.1 website to always run, I think these docs could be updated. For me, the first step that was needed that's not on the hangfire docs is the same first step seen here where you check for the IIS Server Role called Application Initialization: https://www.taithienbo.com/how-to-auto-start-and-keep-an-asp-net-core-web-application-and-keep-it-running-on-iis/. I also did not need to change the CLR version of the app pool from No Managed Code to v4, which I'm glad since it's not recommended by Microsoft. I also did not need to do the last step where you're editing the web.config used by the site, which I'm also glad because it saved me from having to go through the trouble of setting that url dynamically as part of the automated deployments we do.

I'm wondering if others could give their personal experiences as well because I'm frankly not sure if these steps I didn't need to do are required for older versions of ASP.NET Core, or part of older IIS's, or dependent on the code, or anything crazy like that so I'm hesitant to remove them. I'd like to come up with a way to call that out in the docs like 'may not be required' or something like that but not sure how to word it.

[odinserj]

I think we should ask @unionthugface for details, maybe some options aren't required there.