Microsoft Net Framework Service Pack Remove Skin Removal
- Microsoft.NET Framework 3.5 Service Pack 1 is required. How to remove underscore character with awk Is List f() a useful signature? Is there any problem with it / using it? Travelling to Ireland with an Italian 1951 Convention travel document How do I keep my players from focusing too deeply on unimportant details?
- Should I uninstall older version of Microsoft.Net Framework (in my case 2.0 Service Pack 1) beca. If I have a Net 1.0 application and remove Net 1.0 but install Net 2.0.
Windows XP: Click the Remove or Change/Remove tab (to the right of the program). Follow the prompts. A progress bar shows you how long it will take to remove Microsoft.NET Framework Language Pack SP1 - rus.
All apps that host the common language runtime (CLR) need to start, or activate, the CLR in order to run managed code. Typically, a .NET Framework app runs on the version of the CLR that it was built on, but you can change this behavior for desktop apps by using an application configuration file (sometimes referred to as an app.config file). However, you cannot change the default activation behavior for Windows Store apps or Windows Phone apps by using an application configuration file. This article explains how to enable your desktop app to run on another version of the .NET Framework and provides an example of how to target version 4 or later versions.
The version of the .NET Framework that an app runs on is determined in the following order:
Configuration file.
If the application configuration file includes <supportedRuntime> entries that specify one or more .NET Framework versions, and one of those versions is present on the user's computer, the app runs on that version. The configuration file reads <supportedRuntime> entries in the order they are listed, and uses the first .NET Framework version listed that is present on the user's computer. (Use the <requiredRuntime> element for version 1.0.)
Compiled version.
If there is no configuration file, but the version of the .NET Framework that the app was built on is present on the user's computer, the app runs on that version.
Latest version installed.
If the version of the .NET Framework that the app was built on is not present and a configuration file does not specify a version in a <supportedRuntime> element, the app tries to run on the latest version of the .NET Framework that is present on the user's computer.
However, .NET Framework 1.0, 1.1, 2.0, 3.0, and 3.5 apps do not automatically run on the .NET Framework 4 or later, and in some cases, the user may receive an error and may be prompted to install the .NET Framework 3.5. The activation behavior may also depend on the user’s operating system, because different versions of Windows system include different versions of the .NET Framework. If your app supports both the .NET Framework 3.5 and 4 or later, we recommend that you indicate this with multiple entries in the configuration file to avoid .NET Framework initialization errors. For more information, see Versions and Dependencies.
You might also want to configure your .NET Framework 3.5 apps to run on the .NET Framework 4 or later versions, even on computers that have the .NET Framework 3.5 installed, to take advantage of the performance improvements in versions 4 and later versions.
Important
We recommend that you always test your app on every .NET Framework version that you support. See Version Compatibility for information about upgrading your application to support later .NET Framework versions.
For information about modifying your .NET Framework 1.0 and 1.1 apps to support Windows 7 and Windows 8, see Migrating from the .NET Framework 1.1.
To configure your app to run on the .NET Framework 4 or later versions
Add or locate the configuration file for the .NET Framework project. The configuration file for an app is in the same directory and has the same name as the app, but has a .config extension. For example, for an app named MyExecutable.exe, the application configuration file is named MyExecutable.exe.config.
To add a configuration file, on the Visual Studio menu bar, choose Project, Add New Item. Choose General from the left pane, and then choose Configuration File. Name the configuration file appName.exe.config. These menu choices are not available for Windows Store app or Windows phone app projects, because you cannot change the activation policy on those platforms.
Add the <supportedRuntime> element as follows to the application configuration file:
where <version> specifies the CLR version that aligns with the .NET Framework version that your app supports. Use the following strings:
.NET Framework 1.0: 'v1.0.3705'
.NET Framework 1.1: 'v1.1.4322'
.NET Framework 2.0, 3.0, and 3.5: 'v2.0.50727'
.NET Framework 4 and later versions: 'v4.0'
You can add multiple <supportedRuntime> elements, listed in order of preference, to specify support for multiple versions of the .NET Framework.
The following table demonstrates how application configuration file settings and the .NET Framework versions installed on a computer determine the version that a .NET Framework 3.5 app runs on. The examples are specific to a .NET Framework 3.5 application, but you can use similar logic to target applications built with earlier .NET Framework versions. Note that the .NET Framework 2.0 version number (v2.0.50727) is used to specify the .NET Framework 3.5 in the application configuration file.
| App.config file setting | On computer with version 3.5 installed | On computer with versions 3.5 and 4 or later versions installed | On computer with version 4 or later versions installed |
|---|---|---|---|
| None | Runs on 3.5 | Runs on 3.5 | Displays error message that prompts user to install the correct version* |
<supportedRuntime version='v2.0.50727'/> | Runs on 3.5 | Runs on 3.5 | Displays error message that prompts user to install the correct version* |
<supportedRuntime version='v2.0.50727'/><supportedRuntime version='v4.0'/> | Runs on 3.5 | Runs on 3.5 | Runs on 4 or later versions |
<supportedRuntime version='v4.0'/><supportedRuntime version='v2.0.50727'/> | Runs on 3.5 | Runs on 4 or later versions | Runs on 4 or later versions |
<supportedRuntime version='v4.0'/> | Displays error message that prompts user to install the correct version* | Runs on 4 or later versions | Runs on 4 or later versions |
* For more information about this error message and ways to avoid it, see .NET Framework Initialization Errors: Managing the User Experience.
See also
I think its a combination of 3 things that make this problem pop up :
Microsoft Net Framework Update
1. .Net framework 4 and above are standalone frameworks so they do not contain the updates of their older version like 3.5. So even if .Net 4.5 is present on a Windows 8 or Windows Server 2012 machine you still have to install/ enable .Net Framework 3.5.
2. As CozzaroNero mentioned some of the tools/ services in SQL 2012/2014/2016 still require .Net 3.5. In addition if you will notice after the installation of SQL server 2012 a folder of SQL server 2008 is also created in All programs which has Configuration Tools -> Installation Center in it. These tools being from SQL server 2008 still require .Net 3.5
3. Microsoft's decision to have .Net 3.5 not preinstalled/enabled on newer OS's like Windows 8 or Windows server 2012 or else providing the setup of .net 3.5 as a part of the SQL server setup itself( as it was in SQL server 2008 setup).
Net Framework Service Pack 1
Anyways, as a solution I always keep a set of pre-installation scripts that check if .Net 3.5 is installed or not and in case not then it installs it either using DISM.exe in CommandShell or Install-WindowsFeature in PowerShell.