Previously in nopCommerce 4.20 used Out-of-process hosting model for AspNetCoreHostingModel. Although, it was not specified in nopCommerce 4.20. And in ASP.Net Core 2.2 the default value was out-of-process hosting model.
https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/aspnet-core-module?view=aspnetcore-2.2
In ASP.NET Core 3.1 the default value is in-process hosting model.
https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/aspnet-core-module?view=aspnetcore-3.1
The following characteristics apply when hosting in-process:
• The requestTimeout attribute doesn't apply to in-process hosting.
• Sharing an app pool among apps isn't supported. Use one app pool per app.
As nopCommerce 4.30 used In-process hosting model. Now, IIS HTTP Server (IISHttpServer) is used instead of Kestrel server. This leads to not recycle the worker process but instead triggers a graceful shutdown of the current IIS Express process. The next request to the app spawns a new IIS Express process. Which also leads to close IIS Express while restarting application from admin side.
Full information: https://docs.microsoft.com/en-us/aspnet/core/host-and-deploy/aspnet-core-module?view=aspnetcore-3.1#in-process-hosting-model
