Download Visual Studio Community, Professional, and Enterprise. Try Visual Studio IDE, Code or Mac for free today. Visual Studio Code is free and available on your favorite platform - Linux, macOS, and Windows. Download Visual Studio Code to experience a redefined code editor, optimized for building and debugging modern web and cloud applications.
- Visual Studio 2015 For Mac Free Download Windows 7
- Visual Studio Pro 2015 Download
- Visual Studio 2015 Download For Pc
- Visual Studio 2015 For Mac Free Download Windows 10
In this article, you'll learn how to install .NET Core on Windows. .NET Core is made up of the runtime and the SDK. The runtime is used to run a .NET Core app and may or may not be included with the app. The SDK is used to create .NET Core apps and libraries. The .NET Core runtime is always installed with the SDK.
The latest version of .NET Core is 3.1.
Supported releases
The following table is a list of currently supported .NET Core releases and the versions of Windows they're supported on. These versions remain supported until either the version of .NET Core 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.
- A ✔️ indicates that the version of Windows or .NET Core is still supported.
- A ❌ indicates that the version of Windows or .NET Core isn't supported on that Windows release.
- When both a version of Windows and a version of .NET Core have ✔️, that OS and .NET combination are supported.
Operating System | .NET Core 2.1 | .NET Core 3.1 | .NET 5 Preview |
---|---|---|---|
✔️ Windows 10, Version 2004 | ✔️ 2.1 | ✔️ 3.1 | ✔️ 5.0 Preview |
✔️ Windows 10, Version 1909 | ✔️ 2.1 | ✔️ 3.1 | ✔️ 5.0 Preview |
✔️ Windows 10, Version 1903 | ✔️ 2.1 | ✔️ 3.1 | ✔️ 5.0 Preview |
✔️ Windows 10, Version 1809 | ✔️ 2.1 | ✔️ 3.1 | ✔️ 5.0 Preview |
❌ Windows 10, Version 1803 | ✔️ 2.1 | ❌ 3.1 | ❌ 5.0 Preview |
❌ Windows 10, Version 1709 | ❌ 2.1 | ❌ 3.1 | ❌ 5.0 Preview |
❌ Windows 10, Version 1703 | ❌ 2.1 | ❌ 3.1 | ❌ 5.0 Preview |
❌ Windows 10, Version 1607 | ❌ 2.1 | ❌ 3.1 | ❌ 5.0 Preview |
❌ Windows 10, Version 1511 | ❌ 2.1 | ❌ 3.1 | ❌ 5.0 Preview |
❌ Windows 10, Version 1507 | ❌ 2.1 | ❌ 3.1 | ❌ 5.0 Preview |
Unsupported releases
The following versions of .NET Core 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 Core. 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 Core runtime.
Runs ASP.NET Core apps. Includes the .NET Core runtime.
Desktop runtime
Runs .NET Core WPF and .NET Core Windows Forms desktop apps for Windows. Includes the .NET Core runtime.
Runs .NET Core WPF and .NET Core Windows Forms desktop apps for Windows. Includes the .NET Core runtime.
.NET Core 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 Core apps.
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 Core apps.
SDK information
The SDK is used to build and publish .NET Core apps and libraries. Installing the SDK includes all three runtimes: ASP.NET Core, Desktop, and .NET Core.
Dependencies
The following Windows versions are supported with .NET Core 3.1:
OS | Version | Architectures |
---|---|---|
Windows Client | 7 SP1+, 8.1 | x64, x86 |
Windows 10 Client | Version 1609+ | x64, x86 |
Windows Server | 2012 R2+ | x64, x86 |
Nano Server | Version 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:
Note
A
+
symbol represents the minimum version.OS | Version | Architectures |
---|---|---|
Windows Client | 7 SP1+, 8.1 | x64, x86 |
Windows 10 Client | Version 1607+ | x64, x86 |
Windows Server | 2012 R2+ | x64, x86 |
Nano Server | Version 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:
OS | Version | Architectures |
---|---|---|
Windows Client | 7 SP1+, 8.1 | x64, x86 |
Windows 10 Client | Version 1607+ | x64, x86 |
Windows Server | 2008 R2 SP1+ | x64, x86 |
Nano Server | Version 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:
Note
A
+
symbol represents the minimum version.OS | Version | Architectures |
---|---|---|
Windows Client | 7 SP1+, 8.1 | x64, x86 |
Windows 10 Client | Version 1607+ | x64, x86 |
Windows Server | 2008 R2 SP1+ | x64, x86 |
Nano Server | Version 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
- ❌ 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 requirements above 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 Core apps, the following table describes the minimum required version of Visual Studio based on the target .NET Core SDK version.
.NET Core SDK version | Visual Studio version |
---|---|
3.1 | Visual Studio 2019 version 16.4 or higher. |
3.0 | Visual Studio 2019 version 16.3 or higher. |
2.2 | Visual Studio 2017 version 15.9 or higher. |
2.1 | Visual Studio 2017 version 15.7 or higher. |
If you already have Visual Studio installed, you can check your version with the following steps.
- Open Visual Studio.
- Select Help > About Microsoft Visual Studio.
- Read the version number from the About dialog.
Visual Studio can install the latest .NET Core 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.
- Download and install Visual Studio Code.
- Download and install the .NET Core SDK.
- Install the C# extension from the Visual Studio Code marketplace.
Download and manually install
As an alternative to the Windows installers for .NET Core, 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 Core SDK and .NET Core Runtime can be manually installed after they've been downloaded. If you install .NET Core 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:
- ✔️ .NET 5.0 preview downloads
- ✔️ .NET Core 3.1 downloads
- ✔️ .NET Core 2.1 downloads
Create a directory to extract .NET to, for example
%USERPROFILE%dotnet
. Then, extract the downloaded zip file into that directory.By default, .NET Core CLI commands and apps won't use .NET Core 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:
Visual Studio 2015 For Mac Free Download Windows 7
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 Core ignores any globally installed .NET Core version. Remove that environment setting to let .NET Core 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 Core.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 Core can run in a Docker container. Official .NET Core Docker images are published to the Microsoft Container Registry (MCR) and are discoverable at the Microsoft .NET Core 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 Core in a Docker container, see Introduction to .NET and Docker and Samples.
Next steps
- How to check if .NET Core is already installed.
- Tutorial: Hello World tutorial.
- Tutorial: Create a new app with Visual Studio Code.
- Tutorial: Containerize a .NET Core app.
SQL Server Data Tools (SSDT) is a modern development tool for building SQL Server relational databases, databases in Azure SQL, Analysis Services (AS) data models, Integration Services (IS) packages, and Reporting Services (RS) reports. With SSDT, you can design and deploy any SQL Server content type with the same ease as you would develop an application in Visual Studio.
SSDT for Visual Studio 2019
Changes in SSDT for Visual Studio 2019
The core SSDT functionality to create database projects has remained integral to Visual Studio.
With Visual Studio 2019, the required functionality to enable Analysis Services, Integration Services, and Reporting Services projects has moved into the respective Visual Studio (VSIX) extensions only.
Note
There's no SSDT standalone installer for Visual Studio 2019.
Install SSDT with Visual Studio 2019
If Visual Studio 2019 is already installed, you can edit the list of workloads to include SSDT. If you don’t have Visual Studio 2019 installed, then you can download and install Visual Studio 2019 Community.
To modify the installed Visual Studio workloads to include SSDT, use the Visual Studio Installer.
- Launch the Visual Studio Installer. In the Windows Start menu, you can search for 'installer'.
- In the installer, select for the edition of Visual Studio that you want to add SSDT to, and then choose Modify.
- Select SQL Server Data Tools under Data storage and processing in the list of workloads.
For Analysis Services, Integration Services, or Reporting Services projects, you can install the appropriate extensions from within Visual Studio with Extensions > Manage Extensions or from the Marketplace.
SSDT for Visual Studio 2017
Changes in SSDT for Visual Studio 2017
Starting with Visual Studio 2017, the functionality of creating Database Projects has been integrated into the Visual Studio installation. There's no need to install the SSDT standalone installer for the core SSDT experience.
Now to create Analysis Services, Integration Services, or Reporting Services projects, you still need the SSDT standalone installer.
Install SSDT with Visual Studio 2017
To install SSDT during Visual Studio installation, select the Data storage and processing workload, and then select SQL Server Data Tools.
If Visual Studio is already installed, use the Visual Studio Installer to modify the installed workloads to include SSDT.
- Launch the Visual Studio Installer. In the Windows Start menu, you can search for 'installer'.
- In the installer, select for the edition of Visual Studio that you want to add SSDT to, and then choose Modify.
- Select SQL Server Data Tools under Data storage and processing in the list of workloads.
Install Analysis Services, Integration Services, and Reporting Services tools
To install Analysis Services, Integration Services, and Reporting Services project support, run the SSDT standalone installer.
The installer lists available Visual Studio instances to add SSDT tools. If Visual Studio isn't already installed, selecting Install a new SQL Server Data Tools instance installs SSDT with a minimal version of Visual Studio, but for the best experience, we recommend using SSDT with the latest version of Visual Studio.
SSDT for VS 2017 (standalone installer)
Important
Visual Studio Pro 2015 Download
- Before installing SSDT for Visual Studio 2017 (15.9.6), uninstall Analysis Services Projects and Reporting Services Projects extensions if they are already installed, and close all VS instances.
- Removed the inbox component Power Query Source for SQL Server 2017. Now we have announced Power Query Source for SQL Server 2017 & 2019 as out-of-box component, which can be downloaded here.
- To design packages using Oracle and Teradata connectors and targeting an earlier version of SQL Server prior to SQL 2019, in addition to the Microsoft Oracle Connector for SQL 2019 and Microsoft Teradata Connector for SQL 2019, you need to also install the corresponding version of Microsoft Connector for Oracle and Teradata by Attunity.
Release Notes
For a complete list of changes, see Release notes for SQL Server Data Tools (SSDT).
System requirements
SSDT for Visual Studio 2017 has the same system requirements as Visual Studio.
Available Languages - SSDT for VS 2017
This release of SSDT for VS 2017 can be installed in the following languages:
Considerations and limitations
- You can’t install the community version offline
- To upgrade SSDT, you need to follow the same path used to install SSDT. For example, if you added SSDT using the VSIX extensions, then you must upgrade via the VSIX extensions. If you installed SSDT via a separate install, then you need to upgrade using that method.
Offline install
To install SSDT when you’re not connected to the internet, follow the steps in this section. For more information, see Create a network installation of Visual Studio 2017.
First, complete the following steps while online:
- Download the SSDT standalone installer.
- Download vs_sql.exe.
- While still online, execute one of the following commands to download all the files required for installing offline. Using the
--layout
option is the key, it downloads the actual files for the offline installation. Replace<filepath>
with the actual layouts path to save the files.- For a specific language, pass the locale:
vs_sql.exe --layout c:<filepath> --lang en-us
(a single language is ~1 GB). - For all languages, omit the
--lang
argument:vs_sql.exe --layout c:<filepath>
(all languages are ~3.9 GB).
- For a specific language, pass the locale:
After completing the previous steps, the following steps below can be done offline:
- Run
vs_setup.exe --NoWeb
to install the VS2017 Shell and SQL Server Data Project. - From the layouts folder, run
SSDT-Setup-ENU.exe /install
and select SSIS/SSRS/SSAS.a. For an unattended installation, runSSDT-Setup-ENU.exe /INSTALLALL[:vsinstances] /passive
.
For available options, run
SSDT-Setup-ENU.exe /help
Note
If using a full version of Visual Studio 2017, create an offline folder for SSDT only, and run
SSDT-Setup-ENU.exe
from this newly created folder (don’t add SSDT to another Visual Studio 2017 offline layout). If you add the SSDT layout to an existing Visual Studio offline layout, the necessary runtime (.exe) components are not created there.Supported SQL versions
Project Templates | SQL Platforms Supported |
---|---|
Relational databases | SQL Server 2005* - SQL Server 2017 (use SSDT 17.x or SSDT for Visual Studio 2017 to connect to SQL Server on Linux) Azure SQL Database Azure Synapse Analytics (supports queries only; database projects aren't yet supported) * SQL Server 2005 support is deprecated, move to an officially supported SQL version |
Analysis Services models Reporting Services reports | SQL Server 2008 - SQL Server 2017 |
Integration Services packages | SQL Server 2012 - SQL Server 2019 |
DacFx
SSDT for Visual Studio 2015 and 2017 both use DacFx 17.4.1: Download Data-Tier Application Framework (DacFx) 17.4.1.
Previous versions
To download and install SSDT for Visual Studio 2015, or an older version of SSDT, see Previous releases of SQL Server Data Tools (SSDT and SSDT-BI).
Visual Studio 2015 Download For Pc
See Also
Next steps
After installing SSDT, work through these tutorials to learn how to create databases, packages, data models, and reports using SSDT.