The Windows SDK no longer ships with a complete command-line build environment. The Windows SDK now requires a compiler and build environment to be installed separately.
Below that they also list a dozen tools and a bunch of documentation and samples that they also no longer include in the SDK. My guess is that they're just trimming down their SDK downloads. Their SDK has been getting more and more bloated over the years with utilities and samples and stuff that most devs don't need.Completely dropping their command line tools doesn't make sense for anyone who runs build servers; it doesn't make sense for their Powershell tools; and it really doesn't make sense when you consider their recent moves in Open Source. My guess is that the command line tools will be separate downloads from the basic SDK and you'll still be able to write C# code in Notepad++ if you like. The basic SDK will be targeting people writing Metro apps (which they want to encourage by default), but they aren't going to just drop everything else. This is a company that lives and breathes backward compatibility, after all.
It's just a case of poor messaging by Microsoft. Remember last year when everyone thought that all Windows 8 apps were going to be Javascript/HTML 5?
Is the expectation that an IDE as powerful as Visual Studio be given away for free? Or just that the Windows Store not charge a fee for utilizing their distribution infrastructure?
There was a time before Express editions.
edit: I failed to scroll through the rest of the article, feel free to ignore me. I would delete but I don't like stranding replies. Apologies.