Hot answers tagged .net-4.0
If you remove the previous frameworks, then you'll have to edit the application config files of applications that target pre-4.0 frameworks to get them to work. <supportedruntime version="v4.0.x"></supportedruntime> There's an explanation here and here. If you run quite a few .NET programs, I'm sure there are other things on your machine that ...
It turns out that .NET Framework 4 Extended includes an app called PresentationFontCache.exe. This was causing the slow boot and also using a lot of my CPU. I found a fix here - just delete the Font*.dat files from C:\Windows\ServiceProfiles\LocalService\AppData\Local.
The .NET framework releases are generally installable side-by-side per major version. 1.1 is independent of 2.0, which is likewise independent of 4.0. .NET 3.0 and 3.5 were confusing in that they were mostly extensions to 2.0. 4.5 (once released) will install on top of 4.0. That said, Windows 7 comes with .NET 3.5 installed by default (which implicitcly ...
The .NET Framework Client Profile is a subset of the full .NET Framework. When you install the full framework you get the Client Profile plus some additional assemblies which complete the framework. So when say you have the Client Profile + Extended installed, you have the full framework installed. Quoted from MSDN: [The .NET Framework 4 Client ...
Only top voted, non community-wiki answers of a minimum length are eligible