While this is great news, I think alot of damage has already been done by this even happening in the first place. NET in the open and look forward to continuing to work closely with the community. Thank you for all of your feedback and your contributions over the years. When we don’t, the best we can do is learn from our mistakes and be better moving forward. As is true with many companies, we are learning to balance the needs of OSS community and being a corporate sponsor for. Our desire is to create an open and vibrant ecosystem for. We are sorry that we made so many community members upset via this change across many parameters including timing and execution. Thank you for making your feedback heard.
We are always listening to our customers’ feedback to deliver on their needs. 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.
#Will my songs get messed up if i delete maschine library 2 code
In our effort to scope, we inadvertently ended up deleting the source code instead of just not invoking that code path. We made a mistake in executing on this plan in the way it was carried out. NET 6 release and Visual Studio 2022, we chose to focus on bringing Hot Reload to VS2022 first. NET developers are using Visual Studio, and we want to make sure VS delivers the best experience for. 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 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. NET being an open platform and doing our development in the open.
NET 6 SDK.Īs a team, we are committed to. We have approved the pull request to re-enable this code path and it will be in the GA build of the. We made a mistake in executing on our decision and took longer than expected to respond back to the community. NET SDK repo led to a lot of feedback from the community.įirst and foremost, we want to apologize. Last week, our blog post and the removal of the Hot Reload capability from the.
0 kommentar(er)
