我们要道歉。我们在执行决定时犯了一个错误，花了比预期更长的时间来回复社区。我们已经批准了重新启用这一代码路径的拉取请求，它将在 .NET 6 SDK 的 GA 构建中出现。
微软方面解释称，和其他所有的开发团队一样，他们有时必须考虑质量、时间和资源，以便在继续取得进展的同时进行权衡。鉴于绝大多数 .NET 开发人员都在使用 Visual Studio，所以他们希望确保 VS 为 .NET 6 提供最佳体验。
“随着 .NET 6 和 Visual Studio 2022 发布时间的临近，我们选择首先专注于将 Hot Reload 引入 VS2022。我们在执行这个计划的方式上犯了一个错误。在我们的努力范围中，我们无意中删除了源代码，而不是仅仅不调用该代码路径。我们低估了在其跨场景环境中依赖这种能力的开发人员的数量，以及 CLI 是如何与 Visual Studio 一起使用来推动许多人的内循环生产力的。”
在文章的最后，微软再次进行了道歉，并表示：他们的愿望是为 .NET 创造一个开放和充满活力的生态系统。和许多公司一样，他们也正在学习在考虑 OSS 社区的需求和作为 .NET 的企业赞助商之间进行平衡。
“有时，我们无法做到这一点。当我们没有做到的时候，我们能做的就是从我们的错误中学习，并更好地向前发展。感谢大家多年来的所有反馈和贡献。我们致力于在开放中发展 .NET，并期待着继续与社区密切合作。”
原文：
.NET Hot Reload Support via CLI
Last week, our blog post and the removal of the Hot Reload capability from the .NET SDK repo led to a lot of feedback from the community.
First and foremost, we want to apologize. We made a mistake in executing on our decision and took longer than expected to respond back to the community. We have approved the pull request to re-enable this code path and it will be in the GA build of the .NET 6 SDK.
As a team, we are committed to .NET being an open platform and doing our development in the open. The very fact that we decided to adopt an open posture by default from the start for developing the Hot Reload feature is a testament to that. That said, like any development team, from time to time we have to look at quality, time, resources to make tradeoffs while continuing to make forward progress. The vast majority of the .NET developers are using Visual Studio, and we want to make sure VS delivers the best experience for .NET 6.
With the runway getting short for the .NET 6 release and Visual Studio 2022, we chose to focus on bringing Hot Reload to VS2022 first. We made a mistake in executing on this plan in the way it was carried out. In our effort to scope, we inadvertently ended up deleting the source code instead of just not invoking that code path. We underestimated the number of developers that are dependent upon this capability in their environments across scenarios, and how the CLI was being used alongside Visual Studio to drive inner loop productivity by many.
We are always listening to our customers’ feedback to deliver on their needs. Thank you for making your feedback heard. We are sorry that we made so many community members upset via this change across many parameters including timing and execution.
Our desire is to create an open and vibrant ecosystem for .NET. As is true with many companies, we are learning to balance the needs of OSS community and being a corporate sponsor for .NET. Sometimes we don’t get it right. When we don’t, the best we can do is learn from our mistakes and be better moving forward.
Thank you for all of your feedback and your contributions over the years. We are committed to developing .NET in the open and look forward to continuing to work closely with the community.
Thank you!
下一节：IBM 近日宣布，已将其用于公司内部的 ModelMesh 模型服务开源，并贡献给 KServe 开源社区。ModelMesh 专为大规模、高密度和频繁变化的模型用例而设计，可以帮助开发者扩展 Kubernetes。