Earlier quoted context omitted.
As long as it's your deployment target and nothing else. For development, both macOS and Linux continue to be second class citizens, and I don't see this changing as it goes against their interests. In most .NET shops around me, the development and deployment tooling is so closely tied to VS that you can't really not use it. It's fine if you stick to JetBrains and pay for their IDE (or do non-commercial projects only…
Well, in most .NET shops around me: > The development and deployment tooling is so closely tied to VS that you can't really not use it. Development tooling: It's 50-50. Some use Visual Studio, some use Rider. It's fine. The only drawback is that VS Live Share and the Jetbrains equivalent don't interoperate. deployment tooling: There is deployment tooling tied to the IDE? No-one uses that, it seems like a poor idea. I…
VS has the “Publish” functionality for direct deployment to targets. It works well for doing that and nothing else. As you said, CI/CD keeps deployment IDE agnostic and has far more capabilities (e.g. Azure DevOps, GitHub Actions).