I have problems with both. Trusting Visual Studio to build everything means you don't have any idea how to build anything without it. Once you get to C, for some reason you're now writing a makefile to tell the compiler how to feed files to the linker and wrangling with getting it working cross-platform. Or you throw CMake at the problem, but that requires some background knowledge about the ecosystem.

Compared to `cargo build` or `go build`, the GUI-first nature of .net and the build-your-own-toolchain approach of C feel like they're extreme examples of different ends of the spectrum.