Its command-line tools include Git in the package. Users who don’t have Xcode can install it with a single command: xcode-select -install. With Xcode running on your Mac, you can check whether Git is also available by prompting for the Git version: git -version. The output should display the latest Git release, as in the example below.
-->
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.
Unsupported releases
The following versions of .NET are ❌ no longer supported. The downloads for these still remain published:
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:
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.
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:
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. https://evercompany128.weebly.com/blog/macos-notes-app-markdown.
The following Windows versions are supported with .NET Core 2.2: Autodesk desktop app mac.
Note
A
+ symbol represents the minimum version.
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:
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:
Install the following:
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 5.0. 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.
If you already have Visual Studio installed, you can check your version with the following steps.
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:
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.
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. Mac free proxy apps. 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
These advanced steps are primarily for system administrators and others who are familiar with the command line. You don't need a bootable installer to upgrade macOS or reinstall macOS, but it can be useful when you want to install on multiple computers without downloading the installer each time.
![]() What you need to create a bootable installer
Download macOS
Use the 'createinstallmedia' command in Terminal
Installing App Mac Manually From Command Lines
Big Sur:*
Catalina:*
Mojave:*
High Sierra:*
El Capitan:
* If your Mac is using macOS Sierra or earlier, include the
--applicationpath argument and installer path, similar to the way this is done in the command for El Capitan.
After typing the command:
Use the bootable installer
After creating the bootable installer, follow these steps to use it:
Learn more
For more information about the
createinstallmedia command and the arguments that you can use with it, make sure that the macOS installer is in your Applications folder, then enter the appropriate path in Terminal:
Mac Command Line
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |