Visual studio 2017 Update 3 - The SDK 'Microsoft.NET.Sdk.Web' specified could not be found

visual studio 2017 download
visual studio 2019
visual studio 2017 community download
visual studio sdk
.net core sdk
visual studio sdk download
.net framework 4.5 sdk
visual studio 2017 version 15.9 download


C:\WebApp\WebApp.csproj : error : The SDK 'Microsoft.NET.Sdk.Web' specified could not be found. C:\WebApp\WebApp.csproj

I am trying to open Dotnet core project and I am getting the above error.

I have installed the latest SDK from

I have checked the path for dotnet cmd and it works fine.

Am I missing something? Let me know if you need more information.

The target framework is set to .NET 4.5.2

I stumbled upon this issue a number of times recently. Here's a brief list of the workaround I found (one of them always worked until now):

  1. Install the right .NET Core SDK: Either the latest version or the version required by your project.
  2. Clean-up obsolete .NET Core versions: Go to Control Panel and uninstall previous .NET Core SDK/Runtime versions (as long as you don't use them anymore).
  3. Create a Global.json file: Add a new global.json file to your project's root with the following content (replace the .NET Core version build with the one you want to run the project with):

    { "sdk": { "version": "2.0.5" } }

  4. Rename the SDK reference: Open your .proj file and replace <project sdk="Microsoft.NET.Sdk.web"> with <project sdk="Microsoft.NET.Sdk"> .

  5. Add the MSBuildSDKsPath Environment Variable: The dotnet CLI sets the MSBuildSDKsPath environment variable when invoking MSBuild: however, a December 2016 patch changed the CLI behaviour so that it will respect an existing environment variable, if it has already been set: this will allow the developer to "force" the CLI to use a specific SDK.

  6. Check your PATH: Verify that both C:\Program Files\dotnet and C:\Program Files (x86)\dotnet are in the PATH environment variable.

For additional info regarding the issue and other viable fixes check out this blog post that I wrote on this topic.

Download .NET SDKs for Visual Studio, These downloads may update Visual Studio and the . Version, Status, Visual Studio 2017 SDK, Visual Studio 2019 SDK, Runtime, Release notes� Visual studio 2017 Update 3 - The SDK 'Microsoft.NET.Sdk.Web' specified could not be found. Ask Question Asked 2 years, 10 months ago. Active 11 months ago.

As suggested in the comment, I updated global.json file as shown below

  "sdk": {
  "version": "1.0.0"

Also, I had to remove the <ItemGroup> which contains wwwroot files path in .csproj file.

Reload the project and it works like a charm!

Visual studio 2017 Update 3, I stumbled upon this issue a number of times recently. Here's a brief list of the workaround I found (one of them always worked until now):. Visual Studio 2017 SDK Visual Studio 2019 SDK Runtime Release notes.NET 5.0: Preview N/A x64 SDK | x86 SDK (v5.0.100-preview.7) x64 Runtime | x86 Runtime (v5.0.0-preview.7) Release notes.NET Core 3.1: LTS N/A

I agree with the comment on Sundeep's answer, you shouldn't have a global.json file in your project anymore.

It seems as though installing the .NET Core 2.0 SDK is causing issues with the PATH. Verify that C:\Program Files\dotnet and C:\Program Files (x86)\dotnet are in the PATH environment variable. In my case, these values were already present under System Variables so I added them to User Variables and rebooted my machine. This resolved my issue.

Enable .NET Core 3 in Visual Studio 2017 (15.9), UPDATE: This video no longer applies to .NET Core 3 NET Core 3 preview SDKs in Visual Duration: 2:18 Posted: 3 Dec 2018 The Visual Studio SDK helps you extend Visual Studio features or integrate new features into Visual Studio. You can distribute your extensions to other users, as well as to the Visual Studio Marketplace. The following are some of the ways in which you can extend Visual Studio: Add commands, buttons, menus, and other UI elements to the IDE

I've encountered the same problem, I just rename <project sdk="Microsoft.NET.Sdk.web"> to <project sdk="Microsoft.NET.Sdk"> on csproj

another situation:

issue details: 2.1.6xx & 2.2.2xx version of the SDKs are only supported on Visual Studio 2019. VS 2017 needs 2.1.5xx & 2.2.1xx versions of the SDK.

How to fix the issue? Install 2.1.5xx version of the SDK if you are targetting a 2.1 app Install 2.2.1xx version of the SDK if you are targetting a 2.2 app.

and according to the official document:

Note: If you are a Visual Studio user, there are MSBuild version requirements so use only the .NET Core SDK supported for each Visual Studio version. If you use other development environments, we recommend using the latest SDK release.

Installing the Windows SDK Directly From Visual Studio, Install the Windows SDK from Visual Studio version 2013, 2015, or 2017. Extensions and Updates End of the navigation path and enter "SAP SMP" in the� The Visual Studio SDK (Software Development Kit) is an optional feature in Visual Studio setup. You can also install the VS SDK later on. Install the Visual Studio SDK as part of a Visual Studio installation To include the VS SDK in your Visual Studio installation, install the Visual Studio extension development workload under Other Toolsets.

Do not uninstall previous SDK versions!

When I followed the 2nd step suggested in Darkseal's answer, uninstalling the previous SDK versions, it caused an "expected imports are missing" fatal error every time I opened up my project, so I needed to repair my Visual Studio, since installing the old SDK versions again kept popping up this error...

Also the other steps mentioned in that answer did not make any difference (both dotnet references were present in the environment variables and MSBuildSDKsPath was not needed for me).

Install the proper SDK version and select it in the Solution's Properties

As Jyoten mentioned I was using VS2017 x86 version and my SDKs were x64.

However, this was not the only issue, it seems there's some incompatibility with some SDK versions and VS2017. Having installed SDK v2.2.203 and v2.2.202, they would never showed up in the Target framework dropdown when I double-clicked the Properties on my project's solution (in the Solution Explorer (Ctrl+Alt+L)).

So I needed to install v2.2.105 x86 as mentioned in this answer, for it to show up in that dropdown.

Once it did, the solution that was requiring .NET Core v2.2 worked properly (did the Build normally).

The current .NET SDK does not support targeting .NET Core 2.1 , Just installed .net core 3.0 sdk last night and Visual Studio refuses to use it for� Open the Developer command prompt for Visual Studio 2017 or the MSBuild 15.0 command prompt. Build the out-of-box Retail SDK by running msbuild /t:rebuild from the root of the SDK folder (where you can find the dirs.proj file). The folder is RetailSDK\dirs.proj or RetailSDK\Code\dirs.proj in most installations.

Microsoft Windows SDK, Microsoft Windows SDK, and its predecessors Platform SDK, and .NET Framework SDK, are It integrates with Visual Studio, so that multiple copies of the components that both 2016-08-02, [25], Also included in Visual Studio 2015 Update 3 Windows 10 SDK for Fall Creators Update, v10, 10.0.16299.15, 2017-10-10� Update Visual Studio 2017 version 15.5 or earlier. If you're using an earlier version, here's how to apply an update from Visual Studio 2017 version 15.0 through version 15.5. Update by using the Notifications hub. When there are updates, there's a corresponding notification flag in Visual Studio.

Updating your tooling for Windows 10 Creators Update, This includes the Windows 10 Creators Update SDK, Visual Studio 2017 UWP Tooling and Windows Store starting to accept applications that� Refer to your description, please have a look at this: Using the Windows 8 SDK with Visual Studio 2010 – configuring multiple projects and use Property sheets to configure these settings.

VS 2017 (15.7 update), The Visual Studio 2017 (15.7 update) is now available for download, and that VS 2015 Update 3 is binary compatible with VS 2017–code or� To solve it, download and install the SDK for .NET Core 2.1 following the steps below. Also, note that you need to run Visual Studio 2017 15.7 or newer version, as specified in the .NET Core 2.1 download page. Close all running Visual Studio instances. Download the .NET Core SDK from the Microsoft download page. At the time of writing this

  • Did you try this?…
  • I tried removing global.json as suggested in the article and it still didn't work.
  • In case it's helpful - this issue also manifested itself as a permanent hang of Visual Studio while on the Loading project ABC.csproj...
  • New update to VS 2017 tonight might have an answer
  • Why we need to put both path to environment variable?
  • Still an ongoing issue with Visual Studio 15.8.2. This help sort me out - it was the global.json value. Removing the file didn't help, but updating the version number in it did.
  • Before uninstalling older SDK versions (step 2), please read the issues I went through by doing this.
  • In Visual Studio 2019 with Net Core 3.0 preview, I had this issue when I installed only the x64 version. Check…
  • Removing the global.json is probably the best option assuming you always want the latest sdk. In my case I had a misplaced global.json sitting in a folder above the .net core project (probably got placed there by mistake a long time ago). Once I removed that my projects loaded again.
  • In my case, I had the 32 bit runtime and the 64 bit SDK installed, the 32 bit (x86) entry was in the PATH before the 64 bit one. After additionally installing the 32 bit SDK, it worked.
  • I only had the 64-bit SDK installed, but for some reason I only had the 32-bit entry in the Path setting. I tried installing the 32-bit SDK, but ultimately I just added the 64-bit path ahead of the 32-bit one.
  • I have just renamed my dotnet folder in C:\Program Files\dotnet and tried to find what was the problem. Thanks for answer. But also, there is no dotnet folder in C:\Program Files (x86). Interestingly.
  • Thank you for the explanation, this was also my issue. I had to do further steps though, since Darkseal's answer caused me more issues than solved.