I have a question: I am developing with ASP.NET Core 8.0 and have encountered some issues.

1. In a deployed environment, files like (ProjectName).dll are locked, preventing overwriting. I am curious about how others handle deployment in such cases. My goal is zero-downtime deployment.

2. When the DLL is replaced, the site experiences a long period of slow responses. How can I mitigate this issue?

I have tried modifying the web.config and the project .csproj file.

I have a question: I am developing with ASP.NET Core 8.0 and have encountered some issues.

1. In a deployed environment, files like (ProjectName).dll are locked, preventing overwriting. I am curious about how others handle deployment in such cases. My goal is zero-downtime deployment.

2. When the DLL is replaced, the site experiences a long period of slow responses. How can I mitigate this issue?

I have tried modifying the web.config and the project .csproj file.

• deployment
• asp-core-8

1 Answer 1

Usually we will use Network Load Balancing in IIS. And we can access the application via the load balancer url.

Sicne your goal is zero-downtime deployment, we should have 2 node server at least. We can update it one by one.

Related links:

1. HTTP Load Balancing using Application Request Routing

2. Configuring Step 5: Configure Application Deployment