Larry (25+ years on MSFT platforms, mostly in C/C++)
Projects unless you install Visual Studio itself). If you really thought it wasn't required anymore, then why are those tools still installed with Visual Studio 2015 (the latest compiler at this writing) but not the latest standalone SDKs (which are therefore useless for working with 3.5 Do you (MSFT) understand how many people are still working with 3.5 Why would MSFT remove the 3.5 tools from the 8.1 and 10 SDKs in the first place. Visual Studio to get it (because the Windows 7 SDK installation is broken or "unsupported" there).
In my own case, my application requires "al.exe" on a customer's machine and on Windows 10 they'll now be forced to install
Really? Do I really need to install Visual Studio just to pick up the 3.5 version of "al.exe". The Windows 7 SDK doesn't install on Windows 10 of course (the subject of this thread), so you have no choice but to install
Of "al.exe" installed with the Windows 8.1 or 10 SDKs can only create satellite assemblies targeting. For instance, if you want to create a 3.5 or earlier satellite assembly using "al.exe", you either need to install the Windows 7 SDK (and you can even install the tools only if that's all you need), or Visual Studio itself (since the version This is major pain for anyone needing to support. Only the tools targeting 4.X or later are now installed. NET 3.5 or earlier, as they previously were in the Windows 7 SDK. So it appears to work but if you type node -v it will show whichever version is currently in your path variable until you edit the path variable to use 6.4.The Windows 8.1 and 10 SDKs no longer include the tools targeting. * 6.4.0 (Currently using 64-bit executable)
Switching between versions gives a success message but it will not actually work properly unless you manually update the windows system path variable to point to the location that you installed your target version in, for example C:\Users\adamm>nvm list 10.15.1