Only one thing if you could fix in 2020 - Deployment Experience

[naveedahmed1]

Describe the bug

Its not that difficult and painful to make changes in code to upgrade to a new version of .net core than to be able to successfully deploy it on server.

I don't remember any single version of .net/.net core in which I made changes to my code to upgrade, published project, uploaded contents to the server and it worked in first attempt.

1. In case of failed deployment, the error messages are unclear and unfriendly.
2. IIS often locks dll/web.config and other application files and when we have a busy application, we have to wait for ~15-30 min for IIS to release the lock, which results in website downtime. Even app_offline.htm doesn't help.

Honestly this is the only thing I want your team to fix in 2020. If you ask me if I want .Net 5 or a fix for this issue, my response would defiantly be a fix for this issue.

I know there are other issues on this repository, that refers to the same or almost similar issues. But I am still posting it as a new issue so that it can get some priority.

Ideally I want the same deployment experience that we had for Classic ASP about 2 decades ago, in which we just uploaded the files on the server and it always worked.

.Net/Core team has done an excellent job in case of performance and features but unfortunately, deployment experience has become more and more painful with each new release.

Further technical details

• ASP.NET Core version: Its same for all version, even worse with .Net Core 3.x

[JunTaoLuo]

@jkotalik Not sure if we did or plan to do any work in deployment. Putting this in discussion for now since there's no clear work item at the moment.

[jkotalik]

I think this is something we'd like to reevalutate in 6.0.

[ghost]

Thanks for contacting us.
We're moving this issue to the Next sprint planning milestone for future evaluation / consideration. We will evaluate the request when we are planning the work for the next milestone. To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

[jkotalik]

Duplicate of #3793. We are actively working on a PR #28357 that will fix this. We'd appreciate feedback once this feature is available in preview.