Since the production server has restricted access, it wasn't possible that a user was deleting the file. In our scenario, the exe was being deleted, which was causing 502.5 process error as the Host Process couldn't be started. net core framework is bundled in a folder and it also includes your asp.net core Exe which is launched by the IIS server. In a self-contained deployment, the complete. We had recently deployed an Asp.net core 2.x application, which was deployed as a Self-Contained Application. Our problem started when one of our production servers went out of the load balancer. The urge for writing this article comes from an issue in our production environment and it might be useful for readers if ever they encounter such an issue.
0 kommentar(er)
