• Home

Net Runtime 2.0 Download

 

Description SlimDX Runtime.NET (January 2012) 2.0.13.43 can be downloaded from our website for free. SlimDX Runtime.NET (January 2012) lies within Development Tools, more precisely IDE. The following version: 2.0 is the most frequently downloaded one by the program users. The Microsoft.NET Framework version 2.0 redistributable package installs the.NET Framework runtime and associated files required to run applications developed to target the.NET Framework v2.0. 64-bit ODAC 11.2.0.3.20(230,297,429 bytes) Use Oracle Universal Installer (OUI) to deploy via a graphical universal interface. OUI is easy to use and can be configured to install ODAC software silently. 32-bit ODAC OUI can be downloaded from this ODAC developer download page.

-->

.net Core Runtime 2.0 Download Dotnet Core 2.0 Runtime Download The.NET Framework version 2.0 improves scalability and performance of applications with improved caching, application deployment and updating with ClickOnce, support for the broadest array of browsers and devices with ASP.NET 2.0 controls and services. Downloads for building and running applications with.NET Framework. Get web installer, offline installer, and language pack downloads for.NET Framework.

In this article, you'll learn how to install .NET on Windows. .NET is made up of the runtime and the SDK. The runtime is used to run a .NET app and may or may not be included with the app. The SDK is used to create .NET apps and libraries. The .NET runtime is always installed with the SDK.

The latest version of .NET is 5.0.

Supported releases

The following table is a list of currently supported .NET releases and the versions of Windows they're supported on. These versions remain supported until either the version of .NET reaches end-of-support or the version of Windows reaches end-of-life.

Windows 10 versions end-of-service dates are segmented by edition. Only Home, Pro, Pro Education, and Pro for Workstations editions are considered in the following table. Check the Windows lifecycle fact sheet for specific details.

Operating System.NET Core 2.1.NET Core 3.1.NET 5
Windows 10, Version 20H2✔️✔️✔️
Windows 10, Version 2004✔️✔️✔️
Windows 10, Version 1909✔️✔️✔️
Windows 10, Version 1903✔️✔️✔️
Windows 10, Version 1809✔️✔️✔️
Windows 10, Version 1803✔️✔️✔️
Windows 10, Version 1709✔️✔️✔️
Windows 10, Version 1607✔️✔️✔️
Windows 8.1✔️✔️✔️
Windows 7 SP1 ESU✔️✔️✔️
Windows 10, Version 1607✔️✔️✔️
Windows 10, Version 1607✔️✔️✔️
Windows Server 2012 R2✔️✔️✔️
Windows Server Core 2012 R2✔️✔️✔️
Nano Server, Version 1809+✔️✔️✔️
Nano Server, Version 1803✔️✔️

Unsupported releases

The following versions of .NET are ❌ no longer supported. The downloads for these still remain published:

  • 3.0
  • 2.2
  • 2.0

Runtime information

The runtime is used to run apps created with .NET. When an app author publishes an app, they can include the runtime with their app. If they don't include the runtime, it's up to the user to install the runtime.

There are three different runtimes you can install on Windows:

ASP.NET Core runtime
Runs ASP.NET Core apps. Includes the .NET runtime.

Desktop runtime
Runs .NET WPF and Windows Forms desktop apps for Windows. Includes the .NET runtime.

.NET runtime
This runtime is the simplest runtime and doesn't include any other runtime. It's highly recommended that you install both ASP.NET Core runtime and Desktop runtime for the best compatibility with .NET apps.

SDK information

The SDK is used to build and publish .NET apps and libraries. Installing the SDK includes all three runtimes: ASP.NET Core, Desktop, and .NET.

Dependencies

The following Windows versions are supported with .NET 5.0:

OSVersionArchitectures
Windows 10 ClientVersion 1607+x64, x86, ARM64
Windows Client7 SP1+, 8.1x64, x86
Windows Server2012 R2+x64, x86
Windows Server Core2012 R2+x64, x86
Nano ServerVersion 1809+x64

For more information about .NET 5.0 supported operating systems, distributions, and lifecycle policy, see .NET 5.0 Supported OS Versions.

The following Windows versions are supported with .NET Core 3.1:

Note

A + symbol represents the minimum version.

OSVersionArchitectures
Windows Client7 SP1+, 8.1x64, x86
Windows 10 ClientVersion 1607+x64, x86
Windows Server2012 R2+x64, x86
Nano ServerVersion 1803+x64, ARM32

For more information about .NET Core 3.1 supported operating systems, distributions, and lifecycle policy, see .NET Core 3.1 Supported OS Versions.

.NET Core 3.0 is currently ❌ out of support. For more information, see the .NET Core Support Policy.

The following Windows versions are supported with .NET Core 3.0:

OSVersionArchitectures
Windows Client7 SP1+, 8.1x64, x86
Windows 10 ClientVersion 1607+x64, x86
Windows Server2012 R2+x64, x86
Nano ServerVersion 1803+x64, ARM32

For more information about .NET Core 3.0 supported operating systems, distributions, and lifecycle policy, see .NET Core 3.0 Supported OS Versions.

.NET Core 2.2 is currently ❌ out of support. For more information, see the .NET Core Support Policy.

The following Windows versions are supported with .NET Core 2.2:

Note

A + symbol represents the minimum version.

OSVersionArchitectures
Windows Client7 SP1+, 8.1x64, x86
Windows 10 ClientVersion 1607+x64, x86
Windows Server2008 R2 SP1+x64, x86
Nano ServerVersion 1803+x64, ARM32

For more information about .NET Core 2.2 supported operating systems, distributions, and lifecycle policy, see .NET Core 2.2 Supported OS Versions.

The following Windows versions are supported with .NET Core 2.1:

OSVersionArchitectures
Windows Client7 SP1+, 8.1x64, x86
Windows 10 ClientVersion 1607+x64, x86
Windows Server2008 R2 SP1+x64, x86
Nano ServerVersion 1803+x64,

For more information about .NET Core 2.1 supported operating systems, distributions, and lifecycle policy, see .NET Core 2.1 Supported OS Versions.

Windows 7 / Vista / 8.1 / Server 2008 R2 / Server 2012 R2

Additional dependencies are required if you're installing the .NET SDK or runtime on the following Windows versions:

  • Windows 7 SP1 ESU
  • Windows Vista SP 2
  • Windows 8.1
  • Windows Server 2008 R2
  • Windows Server 2012 R2

Install the following:

  • Microsoft Visual C++ 2015 Redistributable Update 3.

The previous requirements are also required if you come across one of the following errors:

The program can't start because api-ms-win-crt-runtime-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem.

- or -

The program can't start because api-ms-win-cor-timezone-l1-1-0.dll is missing from your computer. Try reinstalling the program to fix this problem.

- or -

The library hostfxr.dll was found, but loading it from C:<path_to_app>hostfxr.dll failed.

Install with PowerShell automation

The dotnet-install scripts are used for CI automation and non-admin installs of the runtime. You can download the script from the dotnet-install script reference page.

The script defaults to installing the latest long term support (LTS) version, which is .NET Core 3.1. You can choose a specific release by specifying the Channel switch. Include the Runtime switch to install a runtime. Otherwise, the script installs the SDK.

Install the SDK by omitting the -Runtime switch. The -Channel switch is set in this example to Current, which installs the latest supported version.

Install with Visual Studio

If you're using Visual Studio to develop .NET apps, the following table describes the minimum required version of Visual Studio based on the target .NET SDK version.

.NET SDK versionVisual Studio version
5.0Visual Studio 2019 version 16.8 or higher.
3.1Visual Studio 2019 version 16.4 or higher.
3.0Visual Studio 2019 version 16.3 or higher.
2.2Visual Studio 2017 version 15.9 or higher.
2.1Visual Studio 2017 version 15.7 or higher.

If you already have Visual Studio installed, you can check your version with the following steps.

  1. Open Visual Studio.
  2. Select Help > About Microsoft Visual Studio.
  3. Read the version number from the About dialog.

Visual Studio can install the latest .NET SDK and runtime.

Select a workload

When installing or modifying Visual Studio, select one or more of the following workloads, depending on the kind of application you're building:

  • The .NET Core cross-platform development workload in the Other Toolsets section.
  • The ASP.NET and web development workload in the Web & Cloud section.
  • The Azure development workload in the Web & Cloud section.
  • The .NET desktop development workload in the Desktop & Mobile section.

Install alongside Visual Studio Code

Visual Studio Code is a powerful and lightweight source code editor that runs on your desktop. Visual Studio Code is available for Windows, macOS, and Linux.

While Visual Studio Code doesn't come with an automated .NET Core installer like Visual Studio does, adding .NET Core support is simple.

  1. Download and install Visual Studio Code.
  2. Download and install the .NET Core SDK.
  3. Install the C# extension from the Visual Studio Code marketplace.

Windows Installer

The download page for .NET provides Windows Installer executables.

When you use the MSI files to install .NET< you can customize the installation path by setting the DOTNETHOME_X64 and DOTNETHOME_X86 parameters:

Download and manually install

As an alternative to the Windows installers for .NET, you can download and manually install the SDK or runtime. Manual install is usually performed as part of continuous integration testing. For a developer or user, it's generally better to use an installer.

Both .NET SDK and .NET Runtime can be manually installed after they've been downloaded. If you install .NET SDK, you don't need to install the corresponding runtime. First, download a binary release for either the SDK or the runtime from one of the following sites:

Create a directory to extract .NET to, for example %USERPROFILE%dotnet. Then, extract the downloaded zip file into that directory.

By default, .NET CLI commands and apps won't use .NET installed in this way and you must explicitly choose to use it. To do so, change the environment variables with which an application is started:

This approach lets you install multiple versions into separate locations, then explicitly choose which install location an application should use by running the application with environment variables pointing at that location.

When DOTNET_MULTILEVEL_LOOKUP is set to 0, .NET ignores any globally installed .NET version. Remove that environment setting to let .NET consider the default global install location when selecting the best framework for running the application. The default is typically C:Program Filesdotnet, which is where the installers install .NET.

Docker

Containers provide a lightweight way to isolate your application from the rest of the host system. Containers on the same machine share just the kernel and use resources given to your application.

.NET can run in a Docker container. Official .NET Docker images are published to the Microsoft Container Registry (MCR) and are discoverable at the Microsoft .NET Docker Hub repository. Each repository contains images for different combinations of the .NET (SDK or Runtime) and OS that you can use.

Microsoft provides images that are tailored for specific scenarios. For example, the ASP.NET Core repository provides images that are built for running ASP.NET Core apps in production.

For more information about using .NET in a Docker container, see Introduction to .NET and Docker and Samples.

Next steps

  • How to check if .NET is already installed.
  • Tutorial: Hello World tutorial.
  • Tutorial: Create a new app with Visual Studio Code.
  • Tutorial: Containerize a .NET Core app.

.NET Core 2.2.0 is available for download and usage in your environment. This release includes .NET Core 2.2.0 and .NET Core SDK 2.2.100. Have a look at the Known Issues document as there are a few things to be aware of before installing. All fixes of note can be seen in the .NET Core 2.2.0 commits list.

Blog Round up

The ASP.NET Core side of the team has been hard at work for this release so give the ASP.NET and EF blogs extra attention to learn more about the new features and enhancements.

The .NET Core SDK 2.2.100 includes .NET Core 2.2 Runtime so downloading the runtime packages separately is not needed when installing the SDK. After installing the .NET Core SDK 2.2.100, the following command will show that you're running version 2.2.100 of the tools.

dotnet --version

.net

Your feedback is important and appreciated. We've created an issue at dotnet/core #2098 for your questions and comments.

Downloads

SDK Installer1SDK Binaries1Runtime InstallerRuntime BinariesASP.NET Core Runtime
Windowsx86 x64x86 x64x86 x64x86 x64x86 x64
Hosting Bundle2
macOSx64x64x64x64x641
LinuxSee installations steps belowx64 ARM ARM64 x64 Alpine-x64 ARM ARM64 x64 Alpine]x641 ARM321 x64 Alpine1
RHEL6-x64-x64-
ChecksumsSDK-Runtime--
SymbolsCLI SDK-Runtime Shared Framework Setup-ASP.NET Core

Download Net Framework Runtime 2.0

  1. Includes the .NET Core and ASP.NET Core Runtimes
  2. For hosting stand-alone apps on Windows Servers. Includes the ASP.NET Core Module for IIS and can be installed separately on servers without installing .NET Core runtime.

.net Runtime 2.0 Download

Docker Images

The .NET Core Docker images have been updated for this release. Details on our Docker versioning and how to work with the images can be seen in 'Staying up-to-date with .NET Container Images'.

The following repo has been updated

Net Runtime 2.0 Download

Azure AppServices

Net Runtime 3.5 Download

  • Deployment of .NET Core 2.2.0 to Azure App Services is complete. ANCM (ASP.NET Core Module) deployment is delayed and is expected to complete later in December.