This becomes more of an issue since VC++ 2008 Express is no longer available for download (unless you're an MSDN subscriber), though the compiler itself is still available as part of http://www.microsoft.com/en-us/download/details.aspx?id=3138 (for VC9)

I'll admit I haven't read all the discussion on other issues that relates to this, but I see no reason why the following maps couldn't be tried if vcvarsall.bat is not found. This would at least handle more cases and as far as I can tell is the only realistic option.

VCVARS_TO_WINSDK_BAT = {
    'x86' : 'bin\\vcvars32.bat',
    'amd64' : 'bin\\vcvars64.bat',
    'x86_amd64' : 'bin\\vcvarsx86_amd64.bat',
    'x86_ia64' : 'bin\\vcvarsx86_ia64.bat',
}

VCVARS_TO_VS_BAT = {
    'x86' : 'bin\\vcvars32.bat',
    'amd64' : 'bin\\amd64\\vcvars64.bat',
    'x86_amd64' : 'bin\\x86_amd64\\vcvarsx86_amd64.bat',
    'x86_ia64' : 'bin\\x86_ia64\\vcvarsx86_ia64.bat',
}

I have no idea why, but the SDK installs the batch files into different locations. VCVARS_TO_VS_BAT should be unnecessary, since vcvarsall.bat should always exist in this case, but I see no harm in having more fallback options.

All of these scripts (at least for VC9, VC10 and VC11) will ignore extra arguments.