Tag Info

Hot answers tagged

5

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 ...


5

Ultimately the answer is: there is no such system. Since the user—owner and administrator—of the computer has full control they can fake anything (with sufficient effort) up to and including any attempts by your software to call home for verification. Remember they can always modify your software (including eliminating checks against such modification) as ...


4

Windows will present an error message if the proper framework is not installed. Here is a screenshot of the error message I got when I tried to run an .NET 4.0 app on Windows 7 without .NET 4.


4

You can just install .Net 4.0. Windows 7 comes with 3.5 as standard. Version 4.0 contains backwards compatibility for most applications that aren't extremely advanced.


2

There won't be any problems. They can both be installed on the same PC, without one messing up the other. They install to different folders.


2

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.


2

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 ...


2

Both 4.5 and 4.51 are in-place upgrades, which means they replace the previous version (4 or 4.5). The files are overwritten and these framework versions do not have their own directory but are stored in 'v4.0.30319' So your assumption was absolutely correct.


2

Repair the .Net framework 4.0 in the control panel: Click Start > Control Panel > Programs and Features, select Microsoft .NET Framework 4 Client Profile, and click Uninstall/Change. In the Maintenance screen that opens, choose "Repair .NET Framework 4 Client Project to its original state" and click Next. After the repair completes, click Finish. When you ...


1

You can't have them both, .Net 4.5 is an in-place upgrade to 4.0. References: Compatibility of .NET Framework 4.5 Does .net 4.5 work side by side with .net 4.0? Does installing .NET 4.5 REALLY replace .NET 4.0 assemblies? .NET 4.5 and .NET 4 Won't Coexist


1

Dot net should be installed by default. In windows 7, 3.5 should be there by default. In Win8 4.0 should be there by default. If you need 4, install 4. http://en.wikipedia.org/wiki/.NET_Framework


1

Your log file is outputting an error code that may be caused by a corrupt MSI installer component. You can run the FixIt tool off this page to try and repair it.


1

The CLR.dll version number does not correspond to the .NET framework version number. .NET 4.0 through 4.5.2 will all report 4.0.x for the clr.dll version number. You likely have the correct version installed already. If you really want to be sure, follow this MSDN article "How to: Determine Which .NET Framework Versions Are Installed"


1

Yes, it is safe to delete the folder. You may have to take ownership of the files and change the permissions to allow you to delete the files and folder.


1

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 ...



Only top voted, non community-wiki answers of a minimum length are eligible