I want to move some .NET Core applications to production, and with the old .NET platform you can update the compiled DLL for the application code at any time.
The next time the application pool is redesigned, you will receive a new code - or you can manually restart the application pool.
With .NET Core, it seems that the running application blocks the DLL and cannot be overwritten until the process is closed by inactivity or ends using the task manager (there will be a Windows server).
Is it the preferred way to publish a new version without having to install a maintenance window for all users? This is on a Windows 2012 R2 server running on the .NET Core platform through IIS 8 and an application pool that does not have managed code.
source
share