Previous versions of the Windows SDK have shipped with shortcuts to command windows with environment variables such as FrameworkVersion and WindowsSDKDir that either provide information about the SDK or point to folders within the SDK.
Running a particular version of Visual Studio with a particular SDK could be achieved by opening the appropriate command prompt, and then running the desired version of devenv.
The Windows 8 SDK ships without those command prompts, and without tools like setenv and the Windows SDK Configuration tool. So, how is one supposed to run a particular Visual Studio (e.g., Visual Studio 2010) with Windows SDK 8.0?
I realize I could apply brute force to the problem - e.g., recreate all the environment variables that setenv creates only pointing to the new SDK. But that is inelegant (to say the least). Surely the Windows SDK team didn't expect us all to have to do that?
I have the sneaking suspicion that I'm missing something obvious here :-( Surely the SDK should be easy to use?