Quote:
Originally Posted by AnotherCat
I agree except to add (working from memory) the keys for 3.5 and earlier actually refer to if the features of those versions have been enabled in the current NET pack on Windows 10 or not, not that the NET Pack for the version is installed. On seeing your post I added "features" after "NET 3.5" in my preceding post to hopefully make that clearer.
When one enables NET 3.5 features in Windows 10 it may or may not download extra software to do a rebuild with (just as it may do if enabling other features in Windows or other Microsoft applications).
So, to round it up and to be clear what I am saying (I hope  ). As I understand it when installing any application (I have come across a number) on a Windows 10 machine and it says you have to install NET 3.5 (or earlier) one does not have to install it. One just has to enable it in Windows 10's "Windows Features" (either via "Programs and Features" or by just typing "Windows Features"). The 3.5 and earlier NET Packs will not show as an installed Pack because as far as I am aware the pack is not installed. |
I should have been a bit clearer in that those keys show that the .NET/CLR feature set is available. Those registry keys will be created whether you installed a downloaded .Net install or simply enabled it in Windows features. A program that needs .Net 3.5 could check for the appropriate registry key and if it exists, would not request .Net 3.5 be installed.