Microsoft locks .NET hot reload capabilities behind Visual Studio 2022

• sdk

  117 2,679 10.0 C#

  Core functionality needed to create .NET Core projects, that is shared between Visual Studio and CLI (by dotnet)

  

  This sucks so much. I’ve been happily using dotnet watch hot reload in the .NWT 6 previews, and now they’re removing it (to juice VS usage?). Please upvote: https://github.com/dotnet/sdk/issues/22247

• SaaSHub

  www.saashub.com featured

  SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

  

• vscodium

  545 25,073 9.3 Shell

  binary releases of VS Code without MS branding/telemetry/licensing

  

• pylance-release

  51 1,702 9.2 Python

  Documentation and issues for Pylance

  

  I know some extensions like Pylance are locked to the proprietary version, but I don't see how that's a bait-and-switch if it was developed for use only in the Microsoft distribution.

• WSL

  410 17,316 8.4 PowerShell

  Issues found on WSL

  

  But, as I understand it, hyper-v gets a lock on the Intel VT-x virtualization instruction set/technology, which locks out other virtualization technologies from using it at the same time. https://github.com/microsoft/WSL/issues/5030

• azure-cli

  24 3,986 9.8 Python

  Azure Command-Line Interface

  

  Isn't Azure CLI written in Python?

• splat

  16 969 9.0 C#

  Makes things cross-platform

  

  Head of .NET Foundation creates and merges a PR for a change they made to a project where they hadn't been active for several years. When confronted by current maintainers, their response was at the very least, hostile and poorly thought out.

• core

  111 20,903 9.4 PowerShell

  .NET news, announcements, release notes, and more! (by dotnet)

  

  I'm glad you noticed that. Yes, Microsoft blocking Rider (and other tools) from using VSDBG through licensing has already come to pass. It was glossed over at the time: https://github.com/dotnet/core/issues/505

Suggest a related project