Greg, Yup! That clarifies most of my confusion. So, I need to KEEP: dot-net v2.0 sp2 183MB dot-net v3.0 sp2 169MB dot-net v3.5 sp1 28.23MB AND add dot-net v4.0 Client profile...120MB... :) (380.23MB+120MB=500.23MB) Fine. I deal with 'bloat' all the time... and I still do not understand the benefit of dot-net, yet! I will install v4.0 and push forward.............. :) Thank you for your counsel. Duncan
On 03/07/2012 20:02, Greg Sevart wrote:
Allow me to further confuse things for you. .NET 3.0, 3.5, and 3.5.1 simply extend .NET 2.0. They still use the .NET 2.0 CLR (Common Language Runtime - what actually executes programs written in .NET languages), which in turn is just extended by the later releases in terms of additional features and functionality. .NET 4.0 is a brand new CLR. 2.0, 3.0, 3.5, and 4.0 can (and should) co-exist just fine. You should not clean up or uninstall the prior versions just to install 4.0. Applications that require .NET 3.5 will require 2.0, 3.0, and 3.5 to be installed. Applications that require .NET 4.0 will only require that 4.0 be installed. Short version: Just install 4.0, and leave the "older" versions as-is. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of DSinc Sent: Wednesday, March 07, 2012 6:19 PM To: HWG Subject: [H] MS Dot-Net vX confusion The Collective suggested I embrace MS Dot-Net. Fine. ATM I run v2.0 sp2, v3.0 sp2, and v3.5 sp1. Attempts to remove older versions causes ugly recovery. So, I do not muck with Dot-Net any longer. Yes, I do know that v4.0 exists and is 'optional' per WinUpdates. Now I have my 2011 Turbo Tax SW. It tells me it will download Dot-Net v4.0............... Excuse me? Do I have too much OLD dot-net sw loaded that I really do not need? Should I divorce Dot-Net and optionally install v4.0? Thanks, Duncan
