Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

Use Visual Studio 2017 with .Net Core SDK 2.0

Tags:

Can i open a core 2.0 project in Visual Studio 2017?

I've installed the latest dotnet-core (2.0.0-preview2-005840) and created a core 2.0 console-app.

mkdir dn2cli cd dn2cli dotnet new console dotnet restore 
  • Open console.csproj in Visual Studio 2017 with "open project"
  • Clean and Build Solutions
  • i get several erros
    • amongs others:

Unable to resolve 'Microsoft.NETCore.App (>= 2.0.0)' for '.NETCoreApp,Version=v2.0'.

So. Is it just not supported at the moment or am i missing something?

c:\Temp>dotnet --info  .NET Command Line Tools (2.0.0-preview2-005840)  Product Information:  Version:            2.0.0-preview2-005840  Commit SHA-1 hash:  8f2fcef544  Runtime Environment:  OS Name:     Windows  OS Version:  10.0.14393  OS Platform: Windows  RID:         win10-x86  Base Path:   C:\Program Files (x86)\dotnet\sdk\2.0.0-preview2-005840\  Microsoft .NET Core Shared Framework Host    Version  : 2.0.0-preview1-002061-00   Build    : 2b70ec9c3b014af0c2a5f45de0e5b73a1ae51c09 
like image 863
juwens Avatar asked Apr 25 '17 18:04

juwens


People also ask

Can I use .NET Core in Visual Studio 2017?

Visual Studio 2017 Support for . Among the workloads and project types, you can find support for . NET Framework, . NET Core, Mono, and . NET Native for Universal Windows Platform (UWP).

Does .NET Core 3.1 work with Visual Studio 2017?

Install Visual Studio NET Core 3.1 is having long term support. Visual Studio 2017 supports . NET Core 2.1, whereas Visual Studio 2019 supports both the versions. You can use your favorite IDE, such as Visual Studio, Visual Studio Code, Sublime Text, etc. to develop, restore, build, and run .

Can we use Visual Studio code for .NET Core?

The . NET Core development experience is powered by the C# extension available from the Visual Studio Code Marketplace. To get the extension, press Ctrl-Shift-X / Cmd-Shift-X (all keyboard shortcuts in this guide are for macOS) to open the Extensions pane.


2 Answers

Update:

There is now a VS 2017 15.3 preview that resolves this issue. Starting with VS 15.3, Visual Studio carries an MSBuild SDK resolver that determines which version of the CLI SDK a project would use (e.g. if a global.json sets the version) and uses it's MSBuild targets so new previews are picked up by VS.

Original:

You can modify your environment to get VS 2017 support for the unreleased 2.0 tooling by setting the MSBuildSdksPath as described in https://github.com/aspnet/Announcements/issues/231 so that VS picks up the build logic from the CLI.

like image 136
Martin Ullrich Avatar answered Sep 30 '22 18:09

Martin Ullrich


The Visual Studio .NET Core tools were just released in March, yet the 2.0 preview you are using was released in April. https://blogs.msdn.microsoft.com/dotnet/2017/03/07/announcing-net-core-tools-1-0/ You'll need to wait for an update to the .NET Core Tools before you can use Visual Studio with .NET Core 2.0

like image 30
Novaterata Avatar answered Sep 30 '22 20:09

Novaterata