Setting up a build server is a good indicator really of all these "implicit" dependencies.
File > New C# Project results in a csproj file containing references to MSBuild targets and binaries that supposedly are already installed on the system. While that's a valid assumption on a developer's machine, these dependencies are declared "implicitly". Why not make them explicit and reference the appropriate MSBuild targets and libs from .NET NuGet packages? (really whish .NET gets componentized and shipped through NuGet one day). NuGet package restore could then simply pull in all dependencies required to build the software.
It's not just Microsoft though. Other vendors need to jump on the same bandwagon. Right now, almost nobody really does, definitely nobody who sells to the enterprise market.
https://www.nuget.org/packages/Box.V2/
https://www.nuget.org/packages/DeveloperForce.Common/
https://www.nuget.org/packages/Atlassian.SDK/3.0.0-beta1
Random enterprise names I picked out off the top of my head.
Like all the new stuff, the WebAPIs, EF 6, OData, etc. is now being published as NuGet packages instead of installers or SDKs or whatever.
NuGet seems to be a direct response to this very issue and you constantly mention it.
So what are you asking? After all they can't change the past!