The new tuple syntax in C#7 required the addition lf the ValueTuple class in the framework, but as framework and compiler versions are released independently it has to go into one first. This means people can upgrade their compiler to C#7, and install the ValueTuple nuget package and get the benefit of the new langauge feature without having to move their entire project to require the latest version of the .net framework. I believe the next version of the framework will include ValueTuple by default and the package will no longer be required.
Although at least in this case it will return to being simple at the next release.
But I do see your point, .net has certainly grown in complexity since the early days.
For example, Perl 5 only has barebones support for OOP, and the community developed various approaches to fuller support. It was kind of like the way we've had multiple Javascript frameworks trying out various approaches to MVC. Eventually, Moose[1] was developed and became the most popular approach, and my understanding is that it greatly influenced the core support for OOP in Perl 6.
If you look at the docs for Moose, a lot of the syntax which looks like core language keywords is actually made of functions defined in the module.
This approach is great for letting the community of language users figure out what works and what's needed in the language, so that the language can evolve naturally instead of being designed by a detached committee. Again, it's much like the way Javascript is evolving, where the core language has been picking up features that were originally developed as add-on libraries.