-
Notifications
You must be signed in to change notification settings - Fork 10.9k
Only one thing if you could fix in 2020 - Deployment Experience #17878
Copy link
Copy link
Closed
Labels
ExternalThis is an issue in a component not contained in this repository. It is open for tracking purposes.This is an issue in a component not contained in this repository. It is open for tracking purposes.affected-mediumThis issue impacts approximately half of our customersThis issue impacts approximately half of our customersarea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsenhancementThis issue represents an ask for new feature or an enhancement to an existing oneThis issue represents an ask for new feature or an enhancement to an existing onefeature-iisIncludes: IIS, ANCMIncludes: IIS, ANCMseverity-nice-to-haveThis label is used by an internal toolThis label is used by an internal tool
Milestone
Description
Metadata
Metadata
Assignees
Labels
ExternalThis is an issue in a component not contained in this repository. It is open for tracking purposes.This is an issue in a component not contained in this repository. It is open for tracking purposes.affected-mediumThis issue impacts approximately half of our customersThis issue impacts approximately half of our customersarea-networkingIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsIncludes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractionsenhancementThis issue represents an ask for new feature or an enhancement to an existing oneThis issue represents an ask for new feature or an enhancement to an existing onefeature-iisIncludes: IIS, ANCMIncludes: IIS, ANCMseverity-nice-to-haveThis label is used by an internal toolThis label is used by an internal tool
Type
Fields
No fields configured for issues without a type.
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.
app_offline.htmdoesn'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