It is because of the prerequisites. The . NET 4.0 installer requires the target machine to be updated to.
It is because of the prerequisites. The . NET 4.0 installer requires the target machine to be updated to XP SP3 Vista SP1 Server 2003 SP2 Server 2008 or Win7 The 3.5 SP1 installer is much more lenient, it can even run on the original version of URL1 make that work, it needs to include updates of many of the core Windows components.
A significant chunk of that 231 MB installer are not actually . NET components. Also notable is that in .
NET 4.0, the difference between the client profile and the full version has largely disappeared. The full version is only 15% bigger, there isn't much point in targeting the client profile.
. NET 3.5 is fully backward compatible with . NET 3.0 and .
NET 2.0 - it thus includes all of those two previous versions as well. . NET 4.0, on the other hand, starts from scratch, and can discard deprecated/unnecessary code.
This also means that . NET 4.0 cannot necessarily run . NET 3.5 code unchanged - there's another SO answer on some of the breaking changes there.
This is not accurate, there are no separate versions of the assemblies. All the base assemblies from 2.0 through 3.5 SP1 have assembly version 2.0.0.0 – Hans Passant Jan 13 at 16:44 1 @Hans, indeed. That's why I said 3.5 includes all previous versions (the version of the framework has little to do with the assembly versions) – bdonlan Jan 13 at 16:45.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.